Bug #6516: Expression `/[x]` is not accepted - SaxonJS - Saxonica Developer Community

Actions

Send by e-mail Copy link

Bug #6516

closed

Expression `/[x]` is not accepted

Added by Debbie Lockett 4 months ago. Updated 2 months ago.

Status:

Closed

Priority:

Normal

Assignee:

Debbie Lockett

Category:

XPath Conformance

Sprint/Milestone:

Start date:

2024-08-21

Due date:

% Done:

100%

Estimated time:

Applies to JS Branch:

2, Trunk

Fix Committed on JS Branch:

2, Trunk

Fixed in JS Release:

SaxonJS 2.7

SEF Generated with:

Platforms:

Company:

Contact person:

Additional contact persons:

Description

This bug #6473 reported against Saxon (2024-07-07), is also a bug in SaxonJS:

The expression /[x,y] is apparently legal in XPath 3.1 -- it should be interpreted as the path / (selecting the root node) followed by an array constructor evaluated with that root node as the context item. (One might imagine an alternative interpretation in which [x,y] is interpreted as a predicate filter, but that doesn't parse.)

Saxon rejects this expression with a syntax error.

The expression /map{a:2} also appears to be legal, and is also rejected by Saxon.

The new QT3 tests in prod-PathExpr added for this bug (PathExpr-17 PathExpr-18 PathExpr-19) fail with SaxonJS.

Related issues