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