3 ms·
> But the <noscript> tag itself vanishes during document parsing. This is wrong. In case the browser does not have JS (enabled) its a normal element.
by FlorianRappl 5y ago
> But the <noscript> tag itself vanishes during document parsing.
This is wrong. In case the browser does not have JS (enabled) its a normal element.
- megous 5y agoYes, you can see it in the dev tools/inspector.
- chrismorgan 5y agoI was indeed wrong about this. I’d grown used to uMatrix’s spoofing, where it does get changed, and misrecollected things. I have now refreshed my understanding from the spec: it’s still a parser feature in that that iff scripting is enabled, it parses its children as raw text (like <script> or the old <xmp>). (And then there’s the user-agent style on it, `display: none !important`, so that you can’t get it to appear whatever you do, unlike most normally-hidden tags like head, title and script.) I apologise for misleading people.