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 8059 - "This includes HTML elements in XML documents, even when those documents are in another context (e.g. inside an XSLT transform)" - that seems to conflict with an earlier example saying "if the element is found within a transformation expressed in XSLT (as
Summary: "This includes HTML elements in XML documents, even when those documents are ...
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-25 12:55 UTC by contributor
Modified: 2010-10-04 14:57 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2009-10-25 12:55:47 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#elements-in-the-dom

Comment:
"This includes HTML elements in XML documents, even when those documents are in another context (e.g. inside an XSLT transform)" - that seems to conflict with an earlier example saying "if the element is found within a transformation expressed in XSLT (assuming the user agent also supports XSLT), then the processor would instead treat the script element as an opaque element that forms part of the transform" - it's not an opaque element if the processor has to give it the HTMLScriptElement interface. Which statement is correct?

Posted from: 212.183.140.16
Comment 1 Ian 'Hixie' Hickson 2009-10-27 19:26:59 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.
Comment 2 contributor 2009-10-27 19:28:05 UTC 
Checked in as WHATWG revision r4356.
Check-in comment: Clarify that other specs don't override DOM requirements.
http://html5.org/tools/web-apps-tracker?from=4355&to=4356