Actions
Bug #4442
closed
Shadow attributes on literal result elements
Start date:
2020-01-25
Due date:
% Done:
0%
Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
trunk
Fixed in Maintenance Release:
Platforms:
Description
It appears that when a "standard attribute" such as xsl:default-collation is used on a literal result element, Saxon recognizes the underscore-prefixed variant (here xsl:_default-collation) as a shadow attribute. The specification explicitly disallows this.
Spotted while reading the code (UseWhenFilter.startElement())
Updated by Michael Kay about 4 years ago
False alarm.
Added test case shadow-008, which we are passing.
The first phase of processing incorrectly decides that the element has shadow attributes, which makes it eligible for a second phase of processing, and in the second phase of processing, no shadow attributes are found, so no action is taken.
I will correct the first stage of analysis.
Updated by Michael Kay about 4 years ago
- Status changed from New to Closed
- Fix Committed on Branch trunk added
Please register to edit this issue
Actions
.