Skip to content

Conversation

@flavorjones
Copy link
Member

What problem is this PR intended to solve?

Addresses the bug described in #2324

Commit 1d06b4f introduced NO_EMPTY_TAGS into SaveOptions::DEFAULT_XHTML which libxml2 ignored due to a long-standing bug in serialization.

libxml2 v2.9.11 fixed that serialization bug
(https://gitlab.gnome.org/GNOME/libxml2/-/commit/dc6f009) and started paying attention to the NO_EMPTY_TAGS save option, resulting in seeing output containing, e.g. <col></col> instead of <col/>.

This commit updates the default XHTML save options to drop the NO_EMPTY_TAGS flag, restoring this behavior.

Have you included adequate test coverage?

Yes.

Does this change affect the behavior of either the C or the Java implementations?

This brings the C implementation for libxml >= 2.9.11 back into agreement with the Java implementation.

Commit 1d06b4f introduced NO_EMPTY_TAGS into
SaveOptions::DEFAULT_XHTML which libxml2 ignored due to a
long-standing bug in serialization.

libxml2 v2.9.11 fixed that serialization bug
(https://gitlab.gnome.org/GNOME/libxml2/-/commit/dc6f009) and started
paying attention to the NO_EMPTY_TAGS save option, resulting in seeing
output containing, e.g. `<col></col>` instead of `<col/>`.

This commit updates the default XHTML save options to drop the
NO_EMPTY_TAGS flag, restoring this behavior.

Closes #2324
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants