You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
commit cb2b9cfae3bc335beea7300f813a7f3e0b2776f1
Author: Mike Dalessio <mike.dalessio@gmail.com>
Date: Wed Aug 18 20:12:41 2021 -0400
update CHANGELOG
commit c5074b51f26f9b72bacf11c65f16d637440d93fc
Author: Mike Dalessio <mike.dalessio@gmail.com>
Date: Sat Aug 28 15:19:02 2021 -0400
feat/fix: re-enable namespace_inheritance for Builder documents
This restores the Builder behavior from Nokogiri versions before
1.12.0. This can be switched off by passing a kwarg to the Builder
initializer. See #2317.
commit 3814b47d4c3503cf4960caa2d0c5af84b982ee80
Author: Mike Dalessio <mike.dalessio@gmail.com>
Date: Sat Aug 28 15:15:07 2021 -0400
feat/fix: introduce Document#namespace_inheritance attr
When true, reparented elements without a namespace will inherit their
new parent's namespace (if one exists). Defaults to +false+.
This is part of addressing the behavior change introduced in v1.12 by
1f483f0, allowing us to switch it on or off per-document. See #2317.
See https://nokogiri.org/rdoc/Nokogiri/XML/Builder.html#label-Namespace+inheritance for example
47
+
usage.
48
+
49
+
50
+
#### Downstream gem maintainers
51
+
52
+
Note that any downstream gems may want to specifically omit Nokogiri v1.12.0--v1.12.3 from their dependency specification if they rely on child namespace inheritance:
0 commit comments