On Tue, 25 Aug 2026 06:28:13 GMT, Shruthi Acharya <[email protected]> wrote:
>> When XSLT output method is html, characters supported by the target encoding >> were serialized as HTML entity references (for example, é as eacute;). This >> caused failures when the generated output was later processed as XML. >> >> **Solution:** >> Update HTML serializer to write characters directly when they are supported >> by the configured encoding, and retain existing entity escaping behavior for >> unsupported characters. >> >> **Testing:** >> Verified XSLT transformation with accented characters and confirmed >> generated output can be parsed successfully without XML parsing failures. >> >> Performed Tier1 and Tier2 tests in Linux with and without the fix. No >> regression found >> >> >> The bug report for the same: https://bugs.openjdk.org/browse/JDK-8387291 >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Shruthi Acharya has updated the pull request incrementally with one > additional commit since the last revision: > > Adding a testcase and updating the copyright > > Signed-off-by: Shruthi <[email protected]> I see some test failures: javax/xml/jaxp/functional/test/auctionportal/AuctionItemRepository.java javax/xml/jaxp/unittest/common/prettyprint/PrettyPrintTest.java javax/xml/jaxp/unittest/dom/ls/LSSerializerTest.java Could you verify with Tier2? There are also JCK failures. Please run the JCK tests to verify. ------------- PR Comment: https://git.openjdk.org/jdk/pull/31689#issuecomment-5456427903
