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 6778 - Note the XPath implications of assigning HTML elements into the namespace
Summary: Note the XPath implications of assigning HTML elements into the http://www.w3...
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
Keywords: NoReply
Depends on:
Reported: 2009-04-06 08:34 UTC by Henri Sivonen
Modified: 2010-10-04 14:30 UTC (History)
3 users (show)

See Also:


Description Henri Sivonen 2009-04-06 08:34:51 UTC
In section APIs in HTML documents, please add a note about document.evaluate saying that implementations need to implement the change to XPath reported in bug 6777.
Comment 1 Henri Sivonen 2009-04-06 11:53:13 UTC
Migrated to
Comment 2 Henri Sivonen 2009-04-06 11:54:15 UTC
For clarity, I still think HTML5 should have a note about this. I meant the normative issue is now pending on www-dom instead of bug 6777.
Comment 3 Ian 'Hixie' Hickson 2009-06-01 20:08:58 UTC
What exactly do you want the note to say?
Comment 4 Henri Sivonen 2009-06-02 08:42:32 UTC
In addition to the cases where a name expression would match a node per XPath 1.0, a name expression match evaluate to matching a node when:
 * The name expression has no namespace.
 * The name expression has local name l.
 * The expression is being tested against an element node.
 * The element node has local name l.
 * The element node has namespace
 * The owner document of the element node is an "HTML document".
This is a willful violation of XPath 1.0.
Comment 7 Maciej Stachowiak 2010-03-14 13:18:44 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:

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.