- From: <bugzilla@jessica.w3.org>
- Date: Wed, 20 Oct 2010 10:45:40 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11105 Summary: Prevent execution of scripts in documents that don't have a browsing context after 'already started' has been set Product: HTML WG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: hsivonen@iki.fi QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org In http://www.whatwg.org/specs/web-apps/current-work/#running-a-script before the step "If scripting is disabled for the script element, then the user agent must abort these steps at this point. The script is not executed.", please add a step: "If the Document the element is in is not the active document of a browsing context, then the user agent must abort these steps at this point. The script is not executed." Please also add a note saying that this means scripts in XHR responseXML, scripts in DOMParser-created documents, scripts in documents created by XSLTProcessor::transformToDocument and scripts that are first inserted by a script into a document that has been created with document.implementation.createDocument. Note that what's being proposed here is 2 vs. 1 majority behavior for responseXML, DOMParser and XSLTProcessor::transformToDocument but 1 vs. 2 minority behavior for document.implementation.createDocument. (In the set Gecko, Presto, WebKit that is.) -- Configure bugmail: http://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 Wednesday, 20 October 2010 10:45:46 UTC