Bug 51254

Summary: <noscript> is not allowed inside <p>
Product: WebKit Reporter: Mathias Bynens <mathias>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal    
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: OS X 10.6   
URL: http://jsperf.com/slugs
Attachments:
Description Flags
Screenshot of the error in Web Inspector none

Description Mathias Bynens 2010-12-17 08:08:03 PST 
See http://code.google.com/p/chromium/issues/detail?id=51085:

What steps will reproduce the problem?
1. Open any page with a <noscript> element inside a <p> element
2. Check the Web Inspector

What is the expected result?

No errors or warnings are displayed.

What happens instead?

The Web Inspector displays errors because, apparently, "<noscript> is not allowed inside <p>".

Please provide any additional information below. Attach a screenshot if
possible.

Since this appears to be a WebKit bug, I filed this bug there as well: https://bugs.webkit.org/show_bug.cgi?id=43440

At first, I wasn't sure what to do with this, so I asked #whatwg: http://krijnhoetmer.nl/irc-logs/whatwg/20100803#l-952

# [21:20] <Matjas> What is up with this? Web Inspector gives the following error: "<noscript> is not allowed inside <p>" Screenshot: http://i.imgur.com/rQSRl.png  
# [21:21] <Matjas> But the HTML validates and everything… Is this is a Webkit bug or am I doing something wrong?  
# [21:21] <annevk5> sounds like a WebKit bug  
# [21:23] <Matjas> annevk5: http://www.w3.org/TR/REC-html40/interact/scripts.html#h-18.3.1 says "<!ELEMENT NOSCRIPT - - (%block;)+ "  
# [21:23] <Matjas> (That's from HTML4 though)  
# [21:24] <annevk5> HTML4 does not seem relevant  
# [21:24] <annevk5> and that does not tell anything about what <p> allows  
# [21:24] <annevk5> though I guess if <noscript> just allows %block; <p> does not allow <noscript>  
# [21:24] <annevk5> but still a bug in WebKit
Comment 1 Mathias Bynens 2010-12-17 08:08:56 PST 
Created attachment 76881 [details]
Screenshot of the error in Web Inspector
Comment 2 Mathias Bynens 2010-12-17 08:09:48 PST 

*** This bug has been marked as a duplicate of bug 43440 ***