Open luisherranz opened 3 days ago
Just an update that when we saw work on https://github.com/WordPress/gutenberg/pull/63689 stop we decided to pick up what was there and continue development of a new core/tabs
block. Hopefully (scheduling permitted) I should be able to open up an early PR for review next week. That and https://github.com/WordPress/gutenberg/issues/61297 we're creating for a project we have launching Feb, hoping we can align on those two new iAPI powered blocks for WP 6.8 release.
Wonderful, thanks Seth! 👏
I've added the Dialog block to the list 🙂
https://github.com/WordPress/wordpress-develop/pull/7751 (.length
support on server-processed directives) is ready for review.
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 itarray.length
access in references on the serverdata-wp-class
data-wp-style
Core blocks (priority)
Core blocks (optional)
Bug fixes
WP_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 states