W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > June 2009

[Bug 7059] Forking XPath

From: <bugzilla@wiggum.w3.org>
Date: Sat, 27 Jun 2009 03:38:31 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1MKOkJ-0001hL-IX@wiggum.w3.org>

--- Comment #9 from Michael(tm) Smith <mike@w3.org>  2009-06-27 03:38:31 ---
(In reply to comment #5)
> Here's how I understand the situation:
> * HTML5 changes HTML's processing rules such that it would break any XPath that
> is currently being applied to text/html documents.
> * To keep XPath 1.0 expressions working, therefore, XPath 1.0 implementations
> that implement HTML5 would need to implement some changes.
> * They in fact already do. For example, WebKit does what HTML5 now describes.

So, as a point of clarification: This seems like one of those cases where the
draft is actually descriptively documenting actual existing processing behavior
in at least one major browser, not it in fact unilaterally or arbitrarily
changing the processing rules.

> Personally, I would rather not have to mention XPath in the HTML5 spec; the
> only reason it does mention it is to keep XPath 1.0 working.
> If the XPath working group would rather this text be removed, then I would be
> happy to remove it. Is that the case?

I would be less happy for you to remove it.

I think the reason why Henri requested that it be documented is a good one, I
would like to see us try to come some agreement about how to get resolution on
this, and I think simply removing the text is not a satisfactory resolution.
The value of having the text in there now is for it to get exactly the kind of
wider review that will encourage discussion about the underlying issue that we
need to resolve here.

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 03:38:39 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:37 UTC