> 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?
No. The extensions that are already installed will still work in private windows. It’s only newly installed extensions that are disabled in private windows by default
Firefox 67.0 Released
71–80 of 264 posts
Re: Firefox 67.0 Released
#72Re: Firefox 67.0 Released
#73> 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?
Re: Firefox 67.0 Released
#74Firefox 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
BTW, cheap-ass dark mode can be made by: filter: invert(95%) hue-rotate(190deg) on and perhaps fiddling with some backgrounds, to avoid transparency.
Re: Firefox 67.0 Released
#75Re: Firefox 67.0 Released
#76Firefox 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
BTW, cheap-ass dark mode can be made by: filter: invert(95%) hue-rotate(190deg) on and perhaps fiddling with some backgrounds, to avoid transparency.
Re: Firefox 67.0 Released
#77> "Suspending unused tabs" I'm curious to see how aggressive this is. If it's good enough to render my tab suspender extension obsolete, that'd be fantastic.
> I'm curious to see how aggressive this is. It's in the config parameter's name: browser.tabs.unloadOnLowMemory. Boolean, works only on Windows for now.
Re: Firefox 67.0 Released
#78> 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?
I'm interested in the rationale behind this default. What about extensions make them a possibly bad fit for incognito mode?
Google Chrome has defaulted to disabling extensions in incognito mode as long as I can remember:
> Allow in incognito [ ]
> Warning: Google Chrome cannot prevent extensions from recording your browsing history. To disable this extension in incognito mode, unselect this option.
Re: Firefox 67.0 Released
#79This is great news!
Re: Firefox 67.0 Released
#80>WebRender is gradually enabled by default on Windows 10 desktops with NVIDIA graphics cards Does this mean Webrender in Stable can now be force-enabled for non-Nvidia graphics cards on Windows 10? The language is a little unclear. AFAIK Webrender is available to anyone using Nightly by force enabling it.
It would be better if they offered a way to really turn it off. Firefox has got very crashy in environments that have no access to a GPU.