[wp-trac] [WordPress Trac] #63020: HTML API: Breadcrumbs should include element indices and attributes
WordPress Trac
noreply at wordpress.org
Fri Oct 10 01:40:19 UTC 2025
#63020: HTML API: Breadcrumbs should include element indices and attributes
-------------------------------------------------+-------------------------
Reporter: westonruter | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Future
| Release
Component: HTML API | Version:
Severity: normal | Resolution:
Keywords: has-patch dev-feedback has-test- | Focuses:
info has-unit-tests |
-------------------------------------------------+-------------------------
Comment (by westonruter):
Replying to [comment:13 dmsnell]:
> it seems like the motivating use case is a fairly degenerate form of
XPath which is a kind of custom tracker for a specific element rather than
something that represents normative XPath usage. that’s fine again, in a
plugin, but if that’s the feature leading this design I would love to see
more evidence of universal need for that.
The implementation in Optimization Detective is an XPath subset, yes, but
the breadcrumbs could be used to generate CSS selectors as well or any
more specific breadcrumbs than just an tag name hierarchy.
> now if there’s anything in the HTML API that makes building this custom
subclass difficult I want to see if we can’t align those better.
It has been a few months since I've been in the head space for integration
the HTML Processor. I remember I had tried to subclass to obtain the
breadcrumbs but I encountered issues. Granted, that was a year ago or so.
I need to revisit this and evaluate what need there is for improved
helpers in core, but I won't have time before 6.9-beta1.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/63020#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list