A brief (but not totally inclusive) summary of changes:
Search terms will be displayed in the URL bar when using it for web search.
Enhanced Picture-in-Picture.
Rewind / Fast-forward controls.
Display video duration.
Private windows now block third-party cookies and storage of content trackers.
Passwords automatically generated by Firefox now include special characters.
improved speed, responsiveness, and stability when used with:
Screen readers, as well as certain other accessibility software;
East Asian input methods;
Enterprise single sign-on software; and
Other applications which use accessibility frameworks to access information.
Favicons will now be imported when importing bookmarks from Safari and Chrome-based browsers.
Support for AV1 Image Format files containing animations (AVIS).
Enhanced security for Windows GPU sandbox.
Support for files being drag-and-dropped directly from Microsoft Outlook.
Users on macOS can now access the Services sub-menu directly from Firefox context menus.
On Windows, the elastic overscroll effect has been enabled by default.
Firefox is now available in the Tajik (tg) language.
mozRTCPeerConnection, mozRTCIceCandidate, and mozRTCSessionDescription WebRTC interfaces have been removed.
New CSS functionality, including improved support for the color (level 4) specification (such as the lab(), lch(), oklab(), oklch(), and color() functions) and the scripting media query.
Support for a number of WebRTC features for improved interoperability: RTCMediaSourceStats, RTCPeerConnectionState, RTCPeerConnectionStats (“peer-connection” RTCStatsType), RTCRtpSender.setStreams(), and RTCSctpTransport.
I heard on the grapevine that Firefox would start hiding cookie consent banners automatically in the future. Does anyone know if this is now behind some configuration setting or should one still opt for an extension? I’ve held off on trying any extensions to do this, but as of late it seems like it has gotten worse… What would people even recommend to effectively block these banners?
Seconded. I also liked the Self Destructing Cookies extension, which doesn’t yet work with newer Firefox (though there’s a reimplementation that’s making progress). This had the cookie policy that should be default for all browsers:
When you close a tab, cookies are moved to a separate store.
When you visit the site again, you get a notification pop-up saying ‘cookies from a previous visit were deleted, do you want to restore them?’
If it’s a site that you log into, you tell it to keep the cookies and remain logged in. If it’s a site that you don’t want record anything about you, then you ignore the notification. By default, all cookies are gone as soon as you leave a page but if that wasn’t the right choice for a particular site then there’s an undo button available the next time you return.
I think the undelete bit was the killer feature for Self Destructing Cookies. As a user of a web site, I don’t always know if a feature that it depends on requires cookies until I return, so being able to say ‘oh, oops, I didn’t actually want to delete the cookies from my last visit, restore them and reload the tab please’ meant that it could have a very aggressive deletion default, without ever losing state that I cared about.
For sure, it was definitely better. I hope the rewrite for WebExtensions turns out to be viable.
My flow with Cookie AutoDelete is similar, but at the point of realising “oh, oops, I didn’t actually want to delete the cookies from my last visit” then can quickly add the site to the Cookie AutoDelete Whitelist, and log in again (or set up the site again, etc). Then at least I won’t lose it again.
It’s nowhere near as slick, but at least it only happens at most once per site (and one of the things it’s underscored for me is how few sites I actually want persistent cookies for!)
That’s fine for sites where you have an account and you can restore any state fairly easily, but the self destructing cookies model was really nice for places where I had ephemeral state tied to a cookie, even fairly simple things like shopping basket contents. With richer web apps, state is often stored directly in cookies or HTML5 local storage, or in a server-side back end with a cookie as a key to find it, so losing this is annoying.
I don’t want persistent state for 99% of sites that I visit, but the ones where I do, I often don’t realise it until I return.
I haven’t tried it (I mentioned it in my original post) but the description suggests that it doesn’t support the ‘undo’ mode, which is the thing that made this the perfect cookie-management strategy: delete everything aggressively but give users a way of undoing the deletion after they discover that the cookies contained some state that they’ve lost.
That address bar search thing really took me a moment to notice on the video, but it’s really cool! Doesn’t work for me at all though. And I hope there is a key to toggle it between URL and search term…
It is now possible to override a JavaScript file in the debugger
Here’s a screenshot showing the feature. I have searched ‘test one two three’ using the URL bar on DuckDuckGo. You’ll notice the search terms are there in the URL bar.
Oh, I’m very much aware, but AVIF still not a great format for still images in many categories with the accessibility of hardware encoding as a requirement being the cherry on top. I still want JXL.
A brief (but not totally inclusive) summary of changes:
I always thought the elastic overscroll was part of cocoa. Any timeline on when it will be enabled on GTK?
I think you can enable it manually with
apz.overscroll.enabledinabout:config, but YMMVI heard on the grapevine that Firefox would start hiding cookie consent banners automatically in the future. Does anyone know if this is now behind some configuration setting or should one still opt for an extension? I’ve held off on trying any extensions to do this, but as of late it seems like it has gotten worse… What would people even recommend to effectively block these banners?
You want Consent-o-matic.
https://addons.mozilla.org/en-US/firefox/addon/consent-o-matic/
Seconded. I also liked the Self Destructing Cookies extension, which doesn’t yet work with newer Firefox (though there’s a reimplementation that’s making progress). This had the cookie policy that should be default for all browsers:
If it’s a site that you log into, you tell it to keep the cookies and remain logged in. If it’s a site that you don’t want record anything about you, then you ignore the notification. By default, all cookies are gone as soon as you leave a page but if that wasn’t the right choice for a particular site then there’s an undo button available the next time you return.
You can kind of get that with Temporary Containers but really the ergonomics aren’t quite there.
I think in general containers are a fantastic concept in want of someone figuring out the UX.
It’s not as sophisticated, but Cookie AutoDelete is pretty good.
(It doesn’t automatically keep old cookie for later, but it makes it pretty easy to whitelist domains you want to keep cookies for.)
I think the undelete bit was the killer feature for Self Destructing Cookies. As a user of a web site, I don’t always know if a feature that it depends on requires cookies until I return, so being able to say ‘oh, oops, I didn’t actually want to delete the cookies from my last visit, restore them and reload the tab please’ meant that it could have a very aggressive deletion default, without ever losing state that I cared about.
For sure, it was definitely better. I hope the rewrite for WebExtensions turns out to be viable.
My flow with Cookie AutoDelete is similar, but at the point of realising “oh, oops, I didn’t actually want to delete the cookies from my last visit” then can quickly add the site to the Cookie AutoDelete Whitelist, and log in again (or set up the site again, etc). Then at least I won’t lose it again.
It’s nowhere near as slick, but at least it only happens at most once per site (and one of the things it’s underscored for me is how few sites I actually want persistent cookies for!)
That’s fine for sites where you have an account and you can restore any state fairly easily, but the self destructing cookies model was really nice for places where I had ephemeral state tied to a cookie, even fairly simple things like shopping basket contents. With richer web apps, state is often stored directly in cookies or HTML5 local storage, or in a server-side back end with a cookie as a key to find it, so losing this is annoying.
I don’t want persistent state for 99% of sites that I visit, but the ones where I do, I often don’t realise it until I return.
Is this the reimplementation? https://addons.mozilla.org/en-US/firefox/addon/self-destructing-cookies-webex/ Doesn’t seem very active but gets good reviews
I haven’t tried it (I mentioned it in my original post) but the description suggests that it doesn’t support the ‘undo’ mode, which is the thing that made this the perfect cookie-management strategy: delete everything aggressively but give users a way of undoing the deletion after they discover that the cookies contained some state that they’ve lost.
It’s in nightly. I just updated to 113 and the setting is not yet in stable.
Here’s an article from your favourite grapevine ;). https://lobste.rs/s/igqvhd/firefox_may_soon_reject_cookie_prompts (linked article has instructions)
That address bar search thing really took me a moment to notice on the video, but it’s really cool! Doesn’t work for me at all though. And I hope there is a key to toggle it between URL and search term…
Very cool!
Care to explain? I still don’t get what it’s supposed to show.
Here’s a screenshot showing the feature. I have searched ‘test one two three’ using the URL bar on DuckDuckGo. You’ll notice the search terms are there in the URL bar.
Only works for the default search engine, meh. Most www search engines already have sticky headers so this doesn’t add much.
It works for me on Nightly.
If you’re running 113 and it’s not showing, got to
about:configand enablebrowser.urlbar.showSearchTerms.enabledThat was enabled, but I’ve had to enable
browser.urlbar.showSearchTerms.featureGateactually. (WTF is it gated on, region/language or something?!)And yea, double pressing Esc gives me the URL. Very cool.
Animated AV1 but no JXL 😞
Google has pulled JXL support from Chrome, so it’s a dead letter at this point sadly.
Oh, I’m very much aware, but AVIF still not a great format for still images in many categories with the accessibility of hardware encoding as a requirement being the cherry on top. I still want JXL.