Websites would use more things more liberally if support didn’t lag behind. Used to be that Safari was the new IE9 in that aspect, but Firefox has gradually been getting behind past few years.
How many of these “lacking features” are actually standardized? Of course some draft under development by Google will only work in the latest version of Chrome. It might not even work in future versions of Chrome, since it’s not standardized.
If you built something that requires such a feature, it’s you who is choosing to write code that is incompatible with the standards and only works on a particular browser version. You can’t blame others for that.
Like i said earliier, im a web dev, and that’s a list of web standards, and a comparison which browser has implemented which spec.
You literally said you don’t understand them, so maybe brush up on the subject you are discussing instead of telling others how things are?
I’m not defending anything, just providing info and saying why I use what I use.
If a browser is missing official standards features, then the browser is objectively lagging behind. Yes, the web devs are at fault for using things that lack wider support, but that comes down to many factors such as having the time and money to implement things in a more complex manner to support more browsers. That’s not always feasible or possible if a certain core feature lets us save hours or days.
Websites would use more things more liberally if support didn’t lag behind. Used to be that Safari was the new IE9 in that aspect, but Firefox has gradually been getting behind past few years.
https://caniuse.com/?compare=chrome+135%2Cedge+131%2Csafari+18.3%2Cfirefox+137&compareCats=all
How many of these “lacking features” are actually standardized? Of course some draft under development by Google will only work in the latest version of Chrome. It might not even work in future versions of Chrome, since it’s not standardized.
If you built something that requires such a feature, it’s you who is choosing to write code that is incompatible with the standards and only works on a particular browser version. You can’t blame others for that.
I’m sorry. I don’t think you understand the relationship between a browser and a websites settings.
If a website is not made to be compatible with a certain browser, that is the websites fault. Not the browser.
That link is a wall of checkboxes with no explanation, btw.
(Also, not touching Chrome. Pretty sorry for you that you’re defending it so much.)
Like i said earliier, im a web dev, and that’s a list of web standards, and a comparison which browser has implemented which spec.
You literally said you don’t understand them, so maybe brush up on the subject you are discussing instead of telling others how things are?
I’m not defending anything, just providing info and saying why I use what I use.
If a browser is missing official standards features, then the browser is objectively lagging behind. Yes, the web devs are at fault for using things that lack wider support, but that comes down to many factors such as having the time and money to implement things in a more complex manner to support more browsers. That’s not always feasible or possible if a certain core feature lets us save hours or days.
The web dev guy blames the browser. Classic.
When the browser can’t perform its end of the deal? Certainly. I don’t blame Netflix for no longer supporting IE5, either.
Stick with chromium, dude. Great choice. Crypto Ads for… the win?