[wp-trac] [WordPress Trac] #62653: Add CSS selector based tag navigation to HTML and Tag Processors
WordPress Trac
noreply at wordpress.org
Wed Dec 11 09:20:22 UTC 2024
#62653: Add CSS selector based tag navigation to HTML and Tag Processors
--------------------------------------+------------------------------
Reporter: jonsurrell | Owner: (none)
Type: feature request | Status: new
Priority: normal | Milestone: Awaiting Review
Component: HTML API | Version:
Severity: normal | Resolution:
Keywords: has-patch has-unit-tests | Focuses:
--------------------------------------+------------------------------
Comment (by gziolo):
It's excellent to see progress on this front. It'll further enhance the
developer experience when interacting with HTML API.
I also want to emphasize the more significant impact on WordPress core
when this functionality gets introduced. In practical terms, it means that
eventually, we will be able to read on the server
[https://developer.wordpress.org/block-editor/reference-guides/block-api
/block-attributes/#attribute-source sourced block attributes] from HTML
saved for blocks. This would be a huge win for all the use cases where
developers want to [https://github.com/WordPress/gutenberg/issues/49437
consume blocks as structured data]. The hope is that when all the
development concludes, then when rendering the block on the server, the
developer will have access to the value of every attribute inside
`render_callback` through the `$attributes` param. Additionally, two long-
standing tickets would be simple to implement:
- Expose block data directly through REST API endpoints (#53603). When
retrieving a post via the REST API you could get the block data as part of
the content object instead of the HTML.
- Expand `get_post`'s `$filter` parameter to allow block data as a return
shape (#53602).
--
Ticket URL: <https://core.trac.wordpress.org/ticket/62653#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list