Closed
Bug 484383
Opened 15 years ago
Closed 15 years ago
src="" in <noscript> tag requested when Javascript is enabled.
Categories
(Core :: DOM: HTML Parser, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: locki, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729) src URL's inside a <noscript> tag are currently being requested when Javascript is enabled... Surely the correct action (as both IE and Opera take) should be to ignore everything inside this tag when Javascript is enabled... Reproducible: Always Steps to Reproduce: <noscript><img src="http://file.at/this/location.png"/></noscript> Actual Results: request sent to http://file.at/this/location.png, and resource loaded if successful. Expected Results: ignore referenced file.
Updated•15 years ago
|
Component: General → HTML: Parser
Product: Firefox → Core
QA Contact: general → parser
Comment 1•15 years ago
|
||
Indeed. The patch in bug 484121 will make this a lot easier to fix.
Reporter | ||
Comment 2•15 years ago
|
||
It seems this isn't a bug after-all... I should mention that it only happens when using the XML parser (the HTML parser deals with it as expected), and from reading the (X)HTML5 spec., it looks like the XML parser is in fact showing the correct behaviour : (from) http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-noscript-element ..."All these contortions are required because, for historical reasons, the noscript element is handled differently by the HTML parser based on whether scripting was enabled or not when the parser was invoked. The element is not allowed in XML, because ***in XML the parser is not affected by such state, and thus the element would not have the desired effect.***"
Reporter | ||
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•