XHTML.
Comment on [deleted]
einkorn@feddit.org 5 months agoWhich is a shame. Browser should be strict when rendering.
- Multiple IDs with the same name? Jail!
- Open tags? Jail!
- Invalid order of tags? Believe it or not: Jail!
throwaway@lemmy.cafe 5 months ago
betterdeadthanreddit@lemmy.world 5 months ago
I choose to imagine that these offenses result in developers cooling their heels in the slammer rather than a browser being a picky eater.
__siru__@discuss.tchncs.de 5 months ago
This wsa considered in the earlier days of the web, but then intentionally not enforced. HTML was specifically designed to not fall into the same scheme as most programming languages in that it should try to render what it could even if there was a lot going wrong (unlike most programming languages that try to fail fast).
(And before someone comes after me for comparing HTML to programming languages, I am well aware that it is not Turing complete.)
Dojan@pawb.social 5 months ago
Oh my gods I wish. I was working on a webapp some months ago and was having the weirdest issue with how things were updating. There was a hard to discern pattern to it, but eventually when I really dug into it, I realised that it was generating elements with duplicate IDs, then it all made sense.
If the browser yelled at me, at least in the dev tools, it would’ve saved me a lot of work trying to figure things out.