Google Chrome will limit ad blockers starting June 2024

https://slrpnk.net/post/4222093

Google Chrome will limit ad blockers starting June 2024 - SLRPNK

The “Manifest V3” rollout is back after letting tensions cool for a year.

Google’s sales pitch for Manifest V3 is that, by limiting extensions, the browser can be lighter on resources, and Google can protect your privacy from extension developers.

Emphases mine. Funny, I use extensions to protect my privacy from Google.

The second being Safari, right?

Right?

…right…

Firefox gang rise up!
sad WebKit noises
I really like Orion, which is based on WebKit... but it's Mac only. 😢
As a web developer, Safari needs to either die in a fire or be transferred to a company that actually cares. It’s more than half a decade behind everybody else.

Tell me about it. Every time I implement some new thing in my app:

Firefox/Chrome: You cast HTML5 video. Critical hit!

Safari: Your spell fizzles…

It also took 6 years longer than everybody else to support WebGL2, and it’s the only browser without a working WebGPU implementation. It also has no timeline for wasm-gc, while Chrome already ships with it default enabled and Firefox will ship with it on the next release.

It also has no timeline for wasm-gc

Apple has been removing support for garbage collection from their dev tools. Wouldn’t be surprised if they never add support for that, they’ll tell you not to waste CPU cycles (and therefore, battery power) collecting garbage.

I personally prefer to use such languages, but I often don’t have a choice for certain tech stacks.

… Safari added support for HTMl5 video in 2009.

Chrome did not even exist yet in 2009.

Not looking to start a flame war here, but if that’s the case, then Apple’s had even longer to get it right. lol. I implemented my video containers using the MDN specs which worked for both FF and Chrom(e/ium) as-is. Had to read through Apple-specific specs to figure out why Safari wouldn’t render them (not autoplay but render at all).

Ah - that’s got nothing to do with supported features.

Your video wasn’t working because the default settings (which a user can change) block most video… because safari assumes (correctly) that most video on the web is an ad.

Chrome released in 2008,but did not support HTML5 video until 2010. But yes, Safari did it first (in 2008). en.m.wikipedia.org/wiki/HTML5_video
HTML5 video - Wikipedia

Yeah, when testing my sites, on the desktop at least, I don’t even bother testing in Safari. It ends up with nothing but headaches and a bunch of kludges to make things work there. Reminds me of working with IE years ago. But at least with desktop Safari, it has such a small market share that ignoring it isn’t problematic.
Why would it be? Maybe if you looked at market share just for mobile devices. But on desktop it’s limited to just macOS.

I’m mostly joking.

Mostly.