u/dblohm7

HTTP2 and HTTP3 are always HTTPS.

That doesn’t mean it works the same on mobile. GeckoView works a lot differently than the desktop editions of Gecko.

(That’s also why Fission is not yet enabled by default on mobile: it needs to do a lot more complicated stuff to manage resources)

And that’s also why about:config is hidden on Android release builds: we knew that people would assume that everything works identically on Android as it does on desktop, when that is in fact false.

Use at your own risk!

While in there, be sure to set to true as well, privacy.firstparty.isolate , privacy.resist.fingerprinting and privacy.fingerprintingProtection ! Too bad there is no about:config that opens up in regular mobile Firefox, this change will need to be folded in.

Those are not tested at all.

Not currently, no.

It’s a huge improvement. The parent Firefox process will use more memory, but by and large users should not notice any performance difference versus disabled.

(I worked on the old implementation)

The closed system also has zero effect on crime

You need to understand that customizing your UI with CSS is an unsupported feature. By “unsupported,” it means that there is no guarantee that the underlying structure of the UI won’t change from one version to the next.

Nobody warns you because it should simply be expected.

No, it doesn’t do that. It’s only running as long as you have any Firefox windows open.

What do you mean? Desktop applications don’t stop running every time they become inactive.

Are you sure it’s SpiderMonkey? Are you running tests against the standalone interpreter, or are you running them in the browser?

If it’s the latter, keep in mind that there are probably other browser components involved. But as mentioned elsewhere, performance profiles are the way to find out.

Read the comments elsewhere on this thread. Statcounter is a tracker. Firefox blocks trackers. Do the math.

Mobile.

Lol

Are there any policy settings your registry?

That option can be hidden by policy settings in the registry.

Quite often on this sub I see people changing their page file settings from the default (which is to let the OS automatically adjust the page file size) over to letting them specify an arbitrary maximum size for the page file.

Because of the way Windows works, changing this setting is actually a terrible idea.

Yes. It’s best to just let Windows manage it, tbh.

Your page file is nearly full. Did you change your settings to manually manage it?

I’m not sure that you’re going to get the answers you’re seeking on Reddit; this is not an official forum.

You’d probably be better off discussing this directly with the WebExtensions team on Matrix.

Lol

r/Firefox users: “Why is Mozilla holding back the web?”

Also r/Firefox users: “Why is Mozilla capitulating to Google?”

This sub is awful

You definitely do not want to do that.

Now just imagine that little shit as a lawyer! 🤮

http://www.apa.ca/2017-apa-w5-investigation-calgary.asp

I’m listening…

Yeah, that sounds right to me. (OP, this would be more appropriate for r/Tailscale than this sub).