- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 27 Jun 2009 07:02:08 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7059
Anne <annevk@opera.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |annevk@opera.com
--- Comment #10 from Anne <annevk@opera.com> 2009-06-27 07:02:08 ---
Note also that supporting XPath 2.0 or a new language does not solve the
problem. The problem is legacy XPath 1.0 expressions applying to legacy HTML
content. What changed is that legacy HTML content turns into a namespaced tree
(to make HTML and XHTML more consistent and all sorts of other smallish
benefits) and so we have to change how XPath 1.0 expressions are evaluated
because otherwise the legacy content would break.
Potential solutions:
1. Break with XPath 1.0 as proposed.
2. Abandon the namespaced tree approach.
3. ???
Since 2 is an explicit design goal 1 seems like the best solution, but I'd be
interested in hearing about a potential number 3 given that a) we can keep the
tree namespaced and b) legacy XPath expressions keep working.
--
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 Saturday, 27 June 2009 07:02:17 UTC