Google is weakening ad blockers as part of their MV3 extension standard and this will trickle down into all Chromium browsers. Built in ad blockers lack features compared to uBlock Origin as well.
As a person who cares about css , it’s still a problem. There are so many cool features that everyone has implemented Firefox. I still use FF as my daily driver, because, as you said, duh, but every time I see new stuff added to the spec, I check MDN, and it’ll be all green except Firefox.
I mean, maybe if the Firefox/Chrome market share ratio inverts, ff will suddenly have a lot more pressure to keep up?
I’ve gotten to the point where I don’t even really care about new web features. It’s all come with so much shit that I can’t say the internet today is a better experience than it was back before marketers leaned into it so much and everyone wanting a piece of that data money drowned out much of the rest of it.
I’d take the current feature set with ad blocking and reader mode over any feature set without those. Well, reasonable feature sets. But then again, if I had the option of getting a star trek holodeck but had to let marketers regularly nag me about buying their shit any time I wanted to use it, I’d still be conflicted.
Everything else that has green are still chromium based? Then it’s basically just 1 that has it implemented one that hasn’t
That’s true, but, obviously there’s a market share difference between those two. And the fact that it’s ALWAYS ff that lags behind, it’s not like there’s cool things that ff can do that chrome can’t.
And, more importantly, there’s the browser I like (ff) which doesn’t do the thing, and the browsers I don’t like, which do.
FWIW tho, i don’t think OP will actually apply to ALL chromium browsers. I’ve been using Vivaldi when I cheat on Firefox, and none of the anti-adblock changes Google’s been making have impacted Vivaldi, and I assume that pattern will continue.
You have to remember that sometimes when that shiny new CSS feature comes out, it is underspecced, with unhandled corner cases – “just do what Chromium does” is not a standard – or is it? Having multiple implementations of a spec prove that it is interoperable - without that, you might have a good spec, or you might have a spec that says “whatever Chrome does is what is expected”. Not sure that is what we want from new CSS (or any) features.
You make a compelling point, for sure. There are definitely features that fall into that category (eg page transitions), there are a lot of other things coming out these days that just make life easier.
For example, in chrome (and in the spec) you can now animate between ‘height: [number]’ and ‘height:auto;’ just the other day, I had to write a python function to estimate the highest of a menu based on its length * the line height of the list items, so I could provide an exact height to animate to. It works, but it’s hacky and gross. It would be nice to have access to the solution.
