▲ | masklinn 8 days ago | |||||||||||||||||||||||||||||||||||||||||||||||||
> My favorite is type="module" which competes with the higher level attribute nomodule="true". Anyways it looks like <script> has taken a lot of abuse over the years: It "conflicts" in the same way noscript[1] and script "conflict" no? They're basically related features, but can't really be made exclusive because the mere act of trying to do so wouldn't work: as the link indicates, executing code in a !module browser reserves the type (requires a specific set of types) so you can't use that as a way to opt in !module browsers. [1] an other fun element with wonky parsing rules besides | ||||||||||||||||||||||||||||||||||||||||||||||||||
▲ | themafia 8 days ago | parent [-] | |||||||||||||||||||||||||||||||||||||||||||||||||
You can write:
Which is a little weird. At the very least I'd expect the type="module" documentation to say that `charset`, `defer` and `nomodule` attributes have no effect. | ||||||||||||||||||||||||||||||||||||||||||||||||||
|