Interactivity API iteration for WordPress 6.8 #67276
Labels
[Feature] Interactivity API
API to add frontend interactivity to blocks.
[Type] Iteration
Scoped iteration of an effort from a tracking issue or overview issue ideally for a major release.
In WordPress 6.7, work focused on important improvements to enhance the stability and simplicity of the Interactivity API internals, the introduction of new APIs like
getServerState
/getServerContext
andwp_interactivity_get_element
, improvements to the types, and progress on the Gallery block lightbox and Query block’s Instant Search.In WordPress 6.8, the primary focus will be on:
Work is also continuing to improve the documentation, tracked in the Interactivity API documentation's Tracking Issue.
This is the list of initial tasks, although we will edit this post as we progress and discover other things that we need to do.
Client-side navigation (priority)
data-wp-interactive
in the body.General enhancements
withEvent
and require Interactivity API actions that use the event object to use itwithEvent
and require Interactivity API actions that use theevent
object to use it #64944array.length
access in references on the serverdata-wp-class
data-wp-style
Core blocks (priority)
Core blocks (optional)
Bug fixes
data-wp-each
getsundefined
#67174WP_Interactivity_API::_process_directives()
when there is acore/button
text
block bindingOptional
data-wp-client-only-component
data-wp-slot
anddata-wp-fill
array[0]
access in referencesgetElement()
attributes
navigate()
failure statesnavigate()
Failure States #59856The text was updated successfully, but these errors were encountered: