Actions
Bug #4143
closedDefault for Feature.STRIP_WHITESPACE changed in 9.8 and doesn't match the documentation
Start date:
2019-02-21
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
9.8, 9.9, trunk
Fix Committed on Branch:
9.8, 9.9, trunk
Fixed in Maintenance Release:
Platforms:
Description
The default for Feature.STRIP_WHITESPACE
is documented as ignorable
but since Saxon 9.8, the value returned by
Configuration config = new Configuration();
config.getConfigurationProperty(Feature.STRIP_WHITESPACE);
is "none"
It looks as if the change wasn't intended.
ParseOptions.getStripSpace()
returns Whitespace.IGNORABLE
if the spaceStrippingRule
is null (its initial value),
but Configuration.getConfigurationProperty()
switched to calling ParseOptions.getSpaceStrippingRule()
in 9.8; this returns null, which getConfigurationProperty()
interprets as meaning "none".
Updated by Michael Kay about 5 years ago
- Category set to s9api API
- Status changed from New to Resolved
- Priority changed from Low to Normal
- Applies to branch 9.8, 9.9, trunk added
- Fix Committed on Branch 9.8, 9.9, trunk added
Fixed on 9.8., 9.9, and development branches. Unit test added to ConfigTest.
Updated by O'Neil Delpratt about 5 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 9.9.1.2 added
Bug issue fixed in the Saxon 9.9.1.2 maintenance release.
Please register to edit this issue
Actions