@@ -112,12 +112,13 @@ final class OD_HTML_Tag_Processor extends WP_HTML_Tag_Processor {
112112 * level, however, does introduce the risk of duplicate XPaths being computed. For example, if a theme has a
113113 * `<div id="header" role="banner">` and a `<div id="footer" role="contentinfo">` which are both direct descendants
114114 * of `BODY`, then it is possible for an XPath like `/HTML/BODY/DIV/*[1][self::IMG]` to be duplicated if both of
115- * these `DIV` elements has an `IMG` as the first child. This is also an issue in sites using the Image block
115+ * these `DIV` elements have an `IMG` as the first child. This is also an issue in sites using the Image block
116116 * because it outputs a `DIV.wp-lightbox-overlay.zoom` in `wp_footer`, resulting in there being a real possibility
117- * for XPaths to not be unique in the page. Therefore, en lieu of node index being added to children of `BODY`,
118- * a disambiguating attribute predicate is added for the element's `id`, `role`, or `class` attribute. These three
119- * attributes are the most stable across page loads, especially at the root of the document (where there is no Post
120- * Loop using `post_class()`).
117+ * for XPaths to not be unique in the page. This would similarly be an issue for any theme/plugin that prints a
118+ * `DIV` at the `wp_footer`, again to add a modal, for example. Therefore, en lieu of node index being added to
119+ * children of `BODY`, a disambiguating attribute predicate is added for the element's `id`, `role`, or `class`
120+ * attribute. These three attributes are the most stable across page loads, especially at the root of the document
121+ * (where there is no Post Loop using `post_class()`).
121122 *
122123 * @since 0.4.0
123124 * @see self::get_xpath()
0 commit comments