Caspy7

Yes. They're adding it back to Chrome.

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

Safari is currently lacking animation and progressive decoding - still ahead of everyone else currently.

Looks like by the end of the year we can expect Chrome and Firefox support.

He only mentioned decode complexity. Would be interesting to know the average encode complexity compared to AV1.

Perhaps you meant lossy? Everything I'm seeing says that Opus does not support lossless.

Google Research was central in developing and continuing to push JPEG XL.

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.

Lots of people are using AV1. They just don't know it.

I believe MacOS has full support. Windows now has support available as a free installable plugin.

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.

Goodly amount of static here - unclear to me how much of it is added and how much is original.

https://www.my80stv.com/

Ok, so this is one step in such hyper-fast data transmission. What would be the other hurdles?

*she

They also have a much longer history than Chrome.

Kinda glad they disallowed the extensions that had near unfettered access to browser internals.

I think you're thinking of Firefox.

None that I'm aware of but Firefox has committed to maintaining the more powerful MV2 content blocking APIs that Google is removing.

https://twitter.com/BrendanEich/status/1534893414579249152

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”).

In my experience, most of the time black drawing like that is associated with GPU driver issues.

Certainly a belief among some that soda from a glass bottle tastes notably better.

I'm probably not as technical as the average HN commenter so maybe you can fill me in...

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%?

Apple haven't put it into M1 despite being one of first in the AV1 crowd.

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).

Qualcomm is no supporter of AV1 so they shouldn't have been included in that list. That being said, there's plenty of other hardware makers and licensors in the Alliance.

Confused why you listed Qualcomm as I don't believe they have anything to do with AV1.

If things get bad enough they might use the state of emergency to relax that regulation.

Because it's already enabled on hardware where it's known to work well but disabled where it has issues.

In Firefox Notification prompts can be disabled entirely in settings.

In preferences type 'notifications', click the Settings button and check the box to "Block new requests asking to allow notifications"

'switching to Firefox' isn't something anyone actually has to do. Just start using it for one thing or another and any complete change will happen naturally

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.

This movie is available on Amazon Prime.

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.

Being told you're superior to others your whole life has a tendency to do that.

Lies. I've been reassured by the highest authority in the land that this jet is literally invisible.

Nah. I means Extended Support Release. After Firefox moved to the quicker release train, larger organizations were annoyed because they like stability in order to test stuff prior to release and make sure extensions and everything remains the same. So like Ubuntu (iirc) and some others, they created a Firefox ESR that gets security updates and only major updates ~once a year. I think Thunderbird actually just tracks with Firefox ESR.

I mean, WebRender and spidermonkey are two separate things.

I believe Thunderbird is now ESR. So it gets a major version then security updates for a year until the next one.