W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2009

[Bug 6777] In HTML documents, no-namespace expression must match http://www.w3.org/1999/xhtml nodes

From: <bugzilla@wiggum.w3.org>
Date: Mon, 06 Apr 2009 15:09:21 +0000
To: public-qt-comments@w3.org
Message-Id: <E1LqqRt-0005JJ-Ns@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6777





--- Comment #12 from Henri Sivonen <hsivonen@iki.fi>  2009-04-06 15:09:21 ---
(In reply to comment #10)
> > The important thing is that specs and/or implementations need to change in such
> > a way that existing content that call document.evaluate() doesn't need to
> > change.
> 
> I think you want your DOM3 implementation to use http://www.w3.org/1999/xhtml
> as the default element namespace.
> 
> See http://www.w3.org/TR/xpath20/#dt-def-elemtype-ns.
> 
> I don't think this requires a change to the XPath specification.

Indeed, this would make sense for XPath 2.0. document.evaluate() is constrained
to being compatible with XPath 1.0, though. When I filed this bug, I thought I
should just get this noted in the latest version of XPath without realizing
that document.evaluate() wouldn't be migrating to XPath 2.0 for other reasons.

What would be the best way to approximate the behavior of an XPath 2.0
processor with the http://www.w3.org/1999/xhtml namespace as its default
namespace and with the Compatibility Mode set to true in a processor that is
otherwise only an XPath 1.0 processor?


-- 
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 Monday, 6 April 2009 15:09:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:27 UTC