This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15685 - This does not clearly describe how browsers treat noscript. When scripting is enabled, noscript's contents are escaped, such that less-then, greater-then and ampersands are escaped. Essentially, it is not that noscript can only contain text when scripting
Summary: This does not clearly describe how browsers treat noscript. When scripting is...
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-24 04:44 UTC by contributor
Modified: 2012-07-18 18:47 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2012-01-24 04:44:42 UTC 
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

Comment:
This does not clearly describe how browsers treat noscript. When scripting is
enabled, noscript's contents are escaped, such that less-then, greater-then
and ampersands are escaped. Essentially, it is not that noscript can only
contain text when scripting is enabled, but that its contents are converted to
text. To see this in action, try
document.getElementsByTagName('noscript').innerHTML

Posted from: 64.134.70.8
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.75 Safari/535.7
Comment 1 Ms2ger 2012-01-24 10:18:22 UTC 
Indeed, that is specified in the parsing algorithm.