So, the bug that caused this is bug 2058134. The change that was made there is rather inconvenient for user styling, because now the text painting code simply looks if author styles (e.g the web page author) change the selection color and only then use the css specified colors. I'm pretty sure that means that ::selection does absolutely nothing when used in user{Chrome/Content}.css files because they are user, not author styles.

If you want this changed then you should create a new bug and mark it as being regressed by the above bug.

Absolutely not. If anything, public officials would be the one group whose messaging I would understand being scanned so that the people can sort of keep them on check. But again, implementing such possibility that would still weaken security of everyone else as well so of course it should not actually be done.

Unfortunately by sending DNT you are merely suggesting to the server that you wish to not be tracked. There's no requirement for the server to actually care about you at all.

Now, if DNT were actually legally binding though - that would indeed be very cool.

If a website has a compatible PWA manifest the there will be an item labelled "install" in the three-dot menu of Firefox in place of usual "add to homescreen" item.

Edit: There's a few other requirements as well for the website to be considered installable as PWA, such as it must have a registered service worker so it can work offline. But regardless, if the website provides all the requirements then it can just be installed straight from the menu.

None.

I don't think it's a good idea to take some huge collection of prefs and just apply them blindly.

Instead, make the changes that you actually want to do, so that you actually know what changes you are causing. If you want to put those into your user.js file then feel free, but in my opinion it's just better to change them in about:config directly - that is, unless you need to apply the exact same set of changes to multiple profiles.

Right, but then you shouldn't be shocked to find out that a feature was removed because nobody seemed to be using it.

Also, mobile Firefox has supported PWAs for a long time. I wouldn't say PWAs on desktop would be useless, but they make much more sense on mobile than on desktop.

Yes. I want to have access to both history and bookmarks on all my devices and send specific tabs to other devices. Sync makes these super convenient.

My first guess would be that this is caused by the website implementing its own navigation/history behavior using History API. That can easily mess things up, or at least not behave like you might want.

Also, Servo was originally more or less a testbed for new rendering pathway (webrender) which, when ready, was then integrated into Firefox.

Well the feature development is certainly progressing - here is the tracking bug for it.

You can nowadays just test it in normal nightly without special build - it's extremely incomplete, but you can test it if you wish. It's tied to revorked sidebar which you need to enable in about:config.

Indeed. Also, the auto-open PiP is super nice feature I've been using a lot.

Doesn't really sound like a company that I would want to do any business with then.

Reader mode can show images as well though. I mean, it isn't always successful in doing so - probably because there's about a million different ways a random website could show an image - but reader mode can show images that it thinks are part of the actual content.

I'm guessing that the reason (and a good one at that) is that simply having an option to connect to a local chatbot leads to just confused users because they also need the actual chatbot running on their system. If you can set up that, then you can certainly toggle a simple switch in about:config to show the option.

Also, with mv3 extensions, the extensions that are not actively doing some work are not really "running" in the first place but are just waiting for some event to happen that they have previously told Firefox to inform them about, but there isn't any persistent execution context that is constantly running.

I believe one reason why extension support was not-fully enabled earlier was because mv2 extensions required persistent background context for each extension and that could cause issues if Android just decided to kill that process. But with mv3 the extensions are required to be able to be suspended and then woken up on demand.

Go to about:config and set the pref browser.ml.chat.hideLocalhost to false Afterwards you can select localhost as the provider in Settings > Firefox Labs

Go to about:config and create a new number pref with name ui.prefersReducedMotion and set the value to 0. Afterwards that Firefox profile should use animations even if they are disabled on OS. Works on Windows at least.

Firefox shouldn't force you to restart and update like that unless something else, such as your package manager, has already replaced the executable files on your disk. In such a scenario Firefox doesn't have any option except to inform you to restart it (well I guess it could choose to crash). But the mechanism that forced the update is the package manager.

IIRC the old tab groups feature was eventually removed because telemetry showed that only very few people used it...