this post was submitted on 14 May 2026
141 points (97.3% liked)
Technology
84646 readers
4403 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The industry needs to shift to identifying html, css, and JavaScript versions in browser headers instead of which rendering engine. Saying “I support these versions of these standards” instead of “I’m chromium”.
It’s been a problem since day one. Maybe have some sort of independent certification for each browser to pass before being able to declare that it supports a particular version.
You'd have to indicate "I also support these optional bits" for this to really work, which would lead to truly massive headers.
I prefer the idea of slapping people who put up pages that cater to Chrome rather than reading and following the standards upside the head with a large dead fish. People who write faulty WYSIWYG web design software get smacked once for every bad site deployed with their help.
There shouldn’t be any “optional bits”. Thats part of the problem. Either it’s part of a standard or it’s not. Either you meet the standard for that version number, or you don’t.
The problem is that the standard is fucking huge and maybe your browser supports every feature of version 5xx but is missing a feature related to authentication using guinea pigs introduced in v369. So it would only be allowed to advertise compatibility with v368 even though it can do everything except Guinea pigs.
Realistically you would trim the standard to a core set and advertise compatibility with a version of that and then advertise optional extensions. And that's optional bits if you ask me.
A standard is that, a standard. The amount of moving parts (features?) is irrelevant.
Either it's up to the standard or it isn't.
Then no browser will be "up to" the last 15 years of the standard as none implement all features.
Correct. That is why we're talking about having standards and enforcing them. That's the whole point.
No the point of this discussion is about having one single yes/no question about the standard or a list of features.
So, we're speaking different languages. Got it.