Live data from Hacker News

Firefox 94

mozilla.org

291–300 of 340 posts

Re: Firefox 94

#291
post #259

Earlier quoted context omitted.

Click the gear icon on the New Tab page and turn off Sponsored Shortcuts.

That has never worked for me at least back when i used firefox - the only thing that did work was entirely new tab pages with addons

I think it works now. I did it last week and haven’t seen the sponsored shortcuts reappear.

Re: Firefox 94

#292

Does this release actually enable Fission (process separation) by default? [1] I see it's still turned off in about:config [1]: https://hacks.mozilla.org/2021/05/introducing-firefox-new-si...

To answer my own question: it doesn't, at least not on my system.

I can see the Firefox child process count maxing at around 10 processes with the default fission.autostart set to false:

> ps aux | grep "firefox.*childID" | wc -l

> 10

Also the about:processes page shows some processes containing 'Shared tabs'.

As soon as I flip fission.autostart to true it creates proper separate processes for each tab with the above ps aux command increasing the count as I open up tabs.

Re: Firefox 94

#293
post #80

Earlier quoted context omitted.

IMO this is the correct behavior. Programs should never bother the user with prompts or interruptions of any sort unless absolutely necessary. "Do you want to install this security-critical update to your computer's largest attack surface?" does not rise to that level. The answer is obviously yes, so just do it and don't bother the user. There's probably an advanced setting buried somewhere if you _really_ want to tu…

> There's probably an advanced setting buried somewhere if you _really_ want to turn that behavior off, but why would you? You can create a policy for it { "policies": { "DisableAppUpdate": true } } Create a JSON file called `policies.json` and paste the above code into it. Then place that JSON file in a folder called `distribution`. Then make sure to place the `distribution` folder in the application folder of the b…

typically because its possible these "security" updates will break something unintended. IT teams usually locally test any updates before deploying to an entire infrastructure

Re: Firefox 94

#294
post #25

> We’re rolling out the Firefox Multi-Account Containers extension with Mozilla VPN integration. This lets you use a different server location for each container. This is really cool. I wonder how difficult it would be to allow users to wire this up to arbitrary user-specified VPNs e.g. through WireGuard.

there already is an extension for specifying different proxies per containers: https://addons.mozilla.org/en-US/firefox/addon/container-pro...

Re: Firefox 94

#295
post #10

>On Windows, there will now be fewer interruptions because Firefox won’t prompt you for updates. Instead, a background agent will download and install updates even if Firefox is closed. How considerate of them, I felt I didn't have enough auto-updating background agents yet.

Actually way the background updater is done is much better than most. eg Instead of running its own downloader process, it uses the Windows BITS service to download updates.

People often confuse this feature with the Mozilla Maintenance Service, the latter has shipped with Firefox for more than a decade and is used to avoid UAC prompts during updates.

(I used to work at Mozilla and at one point also worked on the team that owns install/update.)

Re: Firefox 94

#296
post #10

>On Windows, there will now be fewer interruptions because Firefox won’t prompt you for updates. Instead, a background agent will download and install updates even if Firefox is closed. How considerate of them, I felt I didn't have enough auto-updating background agents yet.

They've had the MozillaMaintenance service for several years on Windows already, what has changed now?

(I used to work on the team that owned this)

The maintenance service is used to prevent the need for UAC prompts during upgrades. That's it. No background update functionality.

Re: Firefox 94

#297
post #288
post #207

Earlier quoted context omitted.

It's opt-in AFAIK.

It's opt-out for many -- for me it was enabled by default after an upgrade.

Is it at all possible that you quickly skipped through the dialogue box asking about it when you first opened FF after that upgrade? I only ask because I caught myself almost doing that before I did a double-take.

Re: Firefox 94

#298
post #280
post #273

Quick question (and a bit of an aside): let's say I'm interested in a specific feature being implemented (profile switcher like in chrome, built in feature as in [1], not an add-on as in [2]). How do I go about getting more attention to potentially have this prioritized? Making an account in their bug tracker and spamming the threads sounds annoying, I'd personally get upset if someone did that to my repos or issue t…

(I work for Mozilla. Speaking unofficially.) I don't have a good answer to that question. I guess the straightforward answer would be to make an account on the bug tracker and vote (it's under Details), but my impression is that votes usually don't carry much weight. Oh, and for the reasons you gave, please don't post bug comments in support, unless you really do have additional information or perspective to contribu…

Thank you for your reply!

I've managed to dig up these (that's where https://ideas.mozilla.org redirects me):

- https://mozilla.crowdicity.com/post/719914

- https://mozilla.crowdicity.com/post/724883

Guess it's just a matter of making an account and voting/commenting on these now. The thing is, most people don't go through the trouble of leaving feedback like this. What they do is install Firefox, look into the available functionality, see that there's no profile button, assume the functionality does not exist and call it quits.

Re: Firefox 94

#299

Does this release actually enable Fission (process separation) by default? [1] I see it's still turned off in about:config [1]: https://hacks.mozilla.org/2021/05/introducing-firefox-new-si...

Fission site isolation is not enabled by default in Firefox 94. Since this is a huge change, it's being slowly rolled out to all Firefox 94 users over the next four weeks to watch for bugs. It's already been enabled for 60% of Firefox Nightly users and 40% of Firefox Beta users for a few release cycles.

Re: Firefox 94

#300
post #68

Congrats to the team on shipping site isolation. This required a lot of work on very fundamental parts like frame/page loading.

To clarify, Fission site isolation is not enabled by default in Firefox 94. Since this is a huge change, it's being slowly rolled out to all Firefox 94 users over the next four weeks to watch for bugs. It's already been enabled for 60% of Firefox Nightly users and 40% of Firefox Beta users for a few release cycles.
Post reply on HN