You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even though related I will treat these 2 bugs as separate:
bug (1) (missing error) is caused by the primitive way in which in-scope namespaces are tracked - the solution is fairly trivial - I will tackle this next
bug (2) (false error because xmlns occurs after select attribute) is fixed and awaiting next release. To fix this, when an xmlns declaration is encountered, any 'prefix problems' for the declared prefix that are on the same element as the xmlns declaration are removed.
Fix for bug(1) (missing error) now also fixed on the github repo - bug(1) and bug(2) fixes now awaiting release.
this occurred when any preceding sibling element had an xmlns declaration with that prefix. The preceding sibling erroneously passing on namespace scope could be an element with start/end tags or a self-closed element.
I discovered two issues with namespace declaration scopes and XPath expressions.
First thing is a missing error, that a namespace is undeclared:
The second thing is an error that must not occur:
The text was updated successfully, but these errors were encountered: