- From: <bugzilla@jessica.w3.org>
- Date: Tue, 24 Jan 2012 04:44:42 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15685
Summary: 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
Product: HTML WG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#the
-noscript-element
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: other Hixie drafts (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: contributor@whatwg.org
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org
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
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 24 January 2012 04:44:44 UTC