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 6776 - Note the XSLT implications of assigning HTML elements into the http://www.w3.org/1999/xhtml namespace
Summary: Note the XSLT implications of assigning HTML elements into the http://www.w3....
Status: VERIFIED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: NoReply
Depends on:
Blocks:
 
Reported: 2009-04-06 08:15 UTC by Henri Sivonen
Modified: 2010-10-04 14:48 UTC (History)
3 users (show)

See Also:

Attachments

Description Henri Sivonen 2009-04-06 08:15:28 UTC 
Please add a note the the HTML 5 spec that points out that implementors who implement HTML 5 DOM compliance and implement DOM-to-DOM XSLT transforms need to take into account the things recounted in bug 6775.
Comment 1 Ian 'Hixie' Hickson 2009-06-01 20:08:34 UTC 
Could you elaborate?
Comment 2 Henri Sivonen 2009-06-02 08:38:30 UTC 
Summarizing from bug 6775:

When the output method is "html" (either explicitly or via the defaulting rule in XSLT 1.0), the XSLT processor is outputting into a DOM5 tree and the transformation program outputs an element in no namespace, the processor must (prior to constructing the DOM element node):
1) change the namespace of the element to http://www.w3.org/1999/xhtml
2) ASCII-lowercase the local name of the element
3) ASCII-lowercase the local names of no-namespace attributes on the element
Comment 3 Ian 'Hixie' Hickson 2009-06-02 08:41:15 UTC 
That sounds like a set of requirements that violate XSLT, not a note. Could you clarify? Where would you want these rules?
Comment 4 Henri Sivonen 2009-06-04 08:32:28 UTC 
Yeah, it's a willful violation of XSLT 1.0. However, Gecko already had a willful violation of XSLT 1.0 in this area (for lowercasing). This willful violation needs to be if we want compat with existing content.

I guess the spec text could live near the DOM Core API deltas.
Comment 5 Ian 'Hixie' Hickson 2009-06-26 06:34:59 UTC 
ok, how's that?
Comment 6 Maciej Stachowiak 2010-03-14 13:18:43 UTC 
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, 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

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.