- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 26 Jun 2009 09:24:45 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6777
Henri Sivonen <hsivonen@iki.fi> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #25 from Henri Sivonen <hsivonen@iki.fi> 2009-06-26 09:24:45 ---
(In reply to comment #24)
> So what possible change could you ask for in the XPath 2
> specification?
Since browsers don't implement XPath 2, I no longer ask for any change in XPath
2. Marking this as INVALID.
> It avoids confusing the poor xpath user. If you document something as being
> xpath 1 then the language implemented should be xpath 1, where it is to be
> expected that unprefixed names mean no namespace, and it has been that way for
> 10 years.
Can't do that, since it would break existing Web content. Breaking existing Web
content isn't an option here.
This issue is now addressed by HTML 5:
http://www.whatwg.org/specs/web-apps/current-work/#interactions-with-xpath-and-xslt
(Implemented in Gecko and WebKit.)
--
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 Friday, 26 June 2009 09:24:56 UTC