-
-
Notifications
You must be signed in to change notification settings - Fork 904
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] SAX start_element
behavior changed in libxml v2.12.0
#3148
Comments
Just confirming that this seems to be an upstream issue. I can reproduce it using |
Upstream commit is https://gitlab.gnome.org/GNOME/libxml2/-/commit/e0dd330b which first appeared in libxml 2.12.0
Linked issue is https://gitlab.gnome.org/GNOME/libxml2/-/issues/346 |
I've created an issue upstream: https://gitlab.gnome.org/GNOME/libxml2/-/issues/704 |
start_element
behavior changed in libxml v2.12.0
Fixed upstream in https://gitlab.gnome.org/GNOME/libxml2/-/commit/186562a182d2e27f90631d1a1f63ad5079fe62fb Not sure whether Nick will make a release soon, but if not I can patch this fix into the vendored version in a bugfix release. |
Fix released upstream in v2.12.6, working on a release for that (unrelated blockers exist so it may be a day or two). |
Release imminent, please follow #3151 |
**What problem is this PR intended to solve?** Update to v2.12.6, see https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.12.6 This also makes a small change to `XML::Reader` to accommodate changes in how libxml2 reports the encoding of the Reader (see https://gitlab.gnome.org/GNOME/libxml2/-/issues/697 for details). Closes #3148
v1.16.3 has been released which fixes this: https://github.com/sparklemotion/nokogiri/releases/tag/v1.16.3 |
**What problem is this PR intended to solve?** Update to v2.12.6, see https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.12.6 This also makes a small change to `XML::Reader` to accommodate changes in how libxml2 reports the encoding of the Reader (see https://gitlab.gnome.org/GNOME/libxml2/-/issues/697 for details). Closes #3148 (see related #3151)
Please describe the bug
Originally reported at searls/eiwa#10
The text was updated successfully, but these errors were encountered: