- From: <bugzilla@jessica.w3.org>
- Date: Wed, 07 May 2014 00:10:03 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25582 --- Comment #5 from spiritRKS1910 <crimsteam@gmail.com> --- > The "scripting flag" is a concept that only makes sense for the HTML Parser. > Thus, I think this is correct. The XML namespace-aware parser processing > XHTML will presumably also not execute the script--but here I am less sure, > and will need to check. (Most browsers route the elements created by the XML > Parser that are in the HTML namespace through the same underlying processing > code that handles HTML elements, so this wouldn't surprise me.) If this > turns out to be true I may need to invent something to indicate that this > same flag should be set for XHTML script elements... In other cases (variety of XML) this flag (or behaviour) fit for XHTML script elements (when use correct namespace). >The spec mentions that: > "Additionally, the document must have a URL value equal to the URL of the >active document, a location value of null." > So its "origin" as I think I understand it, is the same as the main > document. I may need to clarify this though?? Yuuup, in fact it should be enough, my mistake. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 7 May 2014 00:10:05 UTC