Running Firefox under Qubes has become increasingly frustrating, as tabs crash whenever (apparently?) they try to use WebGL, or anything that depends on access to a GPU. More and more, Firefox seems to depend on GPU access (or something?) and fails hard when it's not there.
Firefox 67.0 Released
31–40 of 264 posts
Re: Firefox 67.0 Released
#32> Change to extensions in Private Windows: Any new extensions you add to the browser won’t work in Private Windows unless you allow this in the settings. Does this mean that adblocking (and other safety-related) extensions will suddenly stop working on private windows, unless the user knows it has to go to the settings and enable them again?
Looks like it, although if you don't know how to configure your extensions, then why even use them in the first place?
Chrome has been doing this for a while now. You have to check the 'Allow in incognito' button for the extension to work in private mode.
Re: Firefox 67.0 Released
#33Firefox 67 also the first browser that ships with `prefers-color-scheme` (aka dark mode) after Safari. https://developer.mozilla.org/en-US/docs/Web/CSS/@media/pref... And it does the right thing and disables the feature when enabling the resist fingerprinting option. I did a small survey and only very few websites have developed a second dark theme: https://zimbatm.com/DarkMode
Dark mode, for the first time ever, has legitimate, objective reasons to want, now that we have pure LED displays: a black LED pixel consumes no energy.
This Google search frontend has been around long enough to claim it helped save considerable amount of energy on that principle:
What they report about LEDs and CCFL isn't entirely correct, however. It may become in the future.
Technicalities aside, what once could be regarded as an environmental measure, today is a much more practical battery saving strategy.
Re: Firefox 67.0 Released
#34Firefox 67 also the first browser that ships with `prefers-color-scheme` (aka dark mode) after Safari. https://developer.mozilla.org/en-US/docs/Web/CSS/@media/pref... And it does the right thing and disables the feature when enabling the resist fingerprinting option. I did a small survey and only very few websites have developed a second dark theme: https://zimbatm.com/DarkMode
Re: Firefox 67.0 Released
#35Running Firefox under Qubes has become increasingly frustrating, as tabs crash whenever (apparently?) they try to use WebGL, or anything that depends on access to a GPU. More and more, Firefox seems to depend on GPU access (or something?) and fails hard when it's not there.
Re: Firefox 67.0 Released
#36I've tried to switch to Firefox, but I keep running into rendering engine issues with certain sites. It's like it's 2005 again.
Re: Firefox 67.0 Released
#37Firefox 67 also the first browser that ships with `prefers-color-scheme` (aka dark mode) after Safari. https://developer.mozilla.org/en-US/docs/Web/CSS/@media/pref... And it does the right thing and disables the feature when enabling the resist fingerprinting option. I did a small survey and only very few websites have developed a second dark theme: https://zimbatm.com/DarkMode
The new Microsoft Edge has prefers-color-scheme as well.
Re: Firefox 67.0 Released
#38> Save passwords in private browsing mode While this might be handy when visiting your favorite paid porn site, isn't this counter-intuitive? When I am in private mode, I expect nothing to be saved.
In both private and not-private windows, the browser asks the user whether to save each password. Nothing is saved unless you explicitly click the Save button.
What data does the password use retain? IIRC password store retains the "time first used, time last used" and displays that visibly.
In short what's the use-case or user story that fits this feature?
Re: Firefox 67.0 Released
#39Oh! Didn't expect that! Does this mean YubiKeys will now be working in GMail on Firefox?
Together with all the other stuff, this starts to look like a really important and major release of Firefox.
Re: Firefox 67.0 Released
#40I've tried to switch to Firefox, but I keep running into rendering engine issues with certain sites. It's like it's 2005 again.