[cpfohl]

It works that way if you correctly use modern features of CSS/HTML. This is just one of those features. It’s very difficult to correctly update the web platform because backward compatibility is so important for the most widely used programming platform in the world.

[someguy7250]

Lol it's funny to summarize this discussion as: "we don't want to make a (seemingly) positive change because too many people rely on us to live in their 'backwards' ways".

[londons_explore]

Thats fine, but then you say "we're going to make a new html6, and if you put DOCTYPE html6 at the start of your page, then legacy behaviours like that will be dropped and we'll start doing the right thing by default"

[marcosdumay]

And there's absolutely no problem with it. Except that it won't happen due to the standard bodies losing face after they made a lot of noise with their decision that HTML 5 was the one true standard that would never get replaced.

[zlg_codes]

Microsoft also acted like Win10 would be the last one, and here we are with Windows 11. I doubt anyone gave a damn about that. Normies don't have values when faced with not getting their shiny.

What should be more damning, IMO, is that there are barely any grassroots or community members on WHATWG, who has acted like they are more important than W3C. Both have drafted and approved of things that have damaged the Web. I am looking forward to the inevitable protocol split between "linkable documents" and "apps in a common virtual machine". The complexity desired from web app authors is directly opposed to the sort of things that plain HTML and CSS were doing 15-20 years ago.

It'd be nice if Google and friends just worked on the app side of things, on their own protocol, instead of commandeering the Web.