W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2016

[Bug 29655] [XP31] Ambiguous parse for /[x]

From: <bugzilla@jessica.w3.org>
Date: Sat, 21 May 2016 13:48:06 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29655-523-7TUeIIaPqO@http.www.w3.org/Bugs/Public/>

Michael Dyck <jmdyck@ibiblio.org> changed:

           What    |Removed                     |Added
                 CC|                            |jmdyck@ibiblio.org

--- Comment #2 from Michael Dyck <jmdyck@ibiblio.org> ---
(In reply to Michael Kay from comment #0)
> In XPath 3.0, the expression /[x] parsed unambiguously, and selected the
> root node provided it had a child element named x.

I agree with Josh, I don't think that's ever been the case. In order to parse
[x] as a Predicate, it would have to be preceded by a ReverseStep, a
ForwardStep, or a PrimaryExpr, but none of those derive /, a PathExpr.

To get the semantics you describe, you'd have to write (/)[x].

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 21 May 2016 13:48:08 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 21 May 2016 13:48:09 UTC