This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/scripting-1.html Multipage: http://www.whatwg.org/C#the-noscript-element Complete: http://www.whatwg.org/c#the-noscript-element Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: Don't remove script elements when checking noscript What is the point of removing the script elements? It seems to me it affects other parts of the document, e.g. <hgroup><script></script></hgroup> <p><noscript>hello</noscript></p> Removing the script makes the hgroup be invalid. Posted from: 2a00:801:e0:30:280f:e9ec:404a:b94e User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 OPR/21.0.1432.48 (Edition Next)
Hm, yeah, <hgroup> with just a <script> probably shouldn't be valid. It would break in non-script scenarios. That's a good argument for removing it from <hgroup>. Is there anything else this breaks?
I think hgroup is the only odd one.
Let's just drop <script> from <hgroup> then.
Ok, this is done. I just changed h1-h6,script,template to h1-h6,template as the allowed children of <hgroup>. The checkin is going to be delayed because I'm still trying to pin down a very subtle bug in my pipeline.