Caspy7
This last January at FOSDEM there was a panel with representatives from different browser companies. During the panel Kadir Topal, a web platform product manager at Google, indicated that because of the interest they saw in JPEG XL through the Interop Project that they changed their course on supporting it.
https://github.com/web-platform-tests/interop
The video of the panel can be found at https://fosdem.org/2026/schedule/event/7E7387-browser_in_202... . He starts speaking on the issue at about 13:00
Looks like by the end of the year we can expect Chrome and Firefox support.
The Google Chrome folks are the ones who decided to disallow it. You could argue that they are trying to kill it, but certainly not Google at large.
Mozilla said that the current decoder state was unacceptable but if Google Research wrote them a Rust version that met their shippable criteria they'd ship it. That's planned to be done this summer. So I'm optimistic Firefox will ship support (courtesy of Google Research) within the year.
That would just leave Chrome support and Windows to ship by default. I'm hoping Firefox's support would cause pressure on the Chrome team.
Kinda glad they disallowed the extensions that had near unfettered access to browser internals.
> Brave will support uBO and uMatrix so long as Google doesn’t remove underlying V2 code paths (which seem to be needed for Chrome for enterprise support, so should stay in the Chromium open source). Will Google Chrome Web Store really kick them out over V2? We will host if needed.
https://twitter.com/BrendanEich/status/1534905779630661633
> > I’d be interested to hear a plan for Brave on what will happen if upstream removes the code paths needed for pre-v3 ad blockers.
> We could fork them back in at higher maintenance cost. No point in speculating — I don’t write checks of unknown amount and sign them, and Google looks likely to keep V2 support for a year (thanks be to “enterprise”).
I've had personal computers for years and none of them have been on corporate networks so I don't see how MS should care about me in that - and for actual businesses aren't their hardware turnaround times generally less than 5 years? Is this all worth it to shave off that 1%?
Except they weren't. They just paid more money to be considered a "founding" members - assuming that's where you got the idea.
You seem to muse as though AV1 were on the same development track as H265 but delayed. This also doesn't reflect reality. It started well after and had a relatively quick turnaround (as far as codec development goes).
In preferences type 'notifications', click the Settings button and check the box to "Block new requests asking to allow notifications"
This is going to vary with different people. Have you heard the phrase "Default is destiny"? This is especially true for less technical people (the majority of web users).
Personally I'm not going to dabble, rather keeping to the safe and familiar, so I have to intentionally trial run something as my goto/default.
It's not bad, but my recommendation is to go into it with the expectation of a Black Mirror episode rather than something you might pay to see in the cinema.