It is currently Sat Dec 02, 2017 4:08 pm Advanced search
JAB Creations wrote:lyosha, XHTML 1.1 and the noscript element work flawlessly in all browsers for me.
<noscript><script>alert('hello')</script></noscript>
<form><noscript><input name='x' value='y'/></noscript><input type='submit'/></form>
<noscript><meta http-equiv='refresh' content='0; URL=http://example.org/'/></noscript>
<noscript><style>* { color:red }</style></noscript>
Right, that's why you don't experience any problem with it. If you were to use say a hidden form input or various other things that people put in noscript and expect it to not do anything, then I assume you would be surprised that it did something. That's why the element is not allowed at all in XML.JAB Creations wrote:Z, I don't do that stuff with my code though. I just put a divisible and paragraph element inside of the noscript element with some inline styling.
Yeah but then it wouldn't be XML.JAB Creations wrote:Also the whole bit about XHTML not ignoring the noscript element, really parsers ignore XHTML comments <!-- --> so it's only a matter of programming the parser to ignore noscript elements as well...
No, it's just styled as display:none. The XML parser doesn't do anything special for noscript compared to any other element.JAB Creations wrote:as they already do live on my website.
This means you will only able to add to a spec, not redefine it.
Yes. That's been a guiding principle for the WHATWG since its founding. It's even in our charter.
Return to Feedback on the Specs
Users browsing this forum: No registered users and 0 guests