Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interactivity API iteration for WordPress 6.8 #67276

Open
35 tasks
luisherranz opened this issue Nov 25, 2024 · 3 comments
Open
35 tasks

Interactivity API iteration for WordPress 6.8 #67276

luisherranz opened this issue Nov 25, 2024 · 3 comments
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.

Comments

@luisherranz
Copy link
Member

luisherranz commented Nov 25, 2024


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 and wp_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:

  1. Enhancing client-side navigation, advancing full page client-side navigation while addressing and improving the limitations of region-based client-side navigation.
  2. Finishing the lightbox of the Gallery Block and the Instant Search functionality for the Query and Search Blocks.

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)

  • Review how to inject data-wp-interactive in the body.
  • Review region-based settings (like the Query block) when full-page is enabled.
  • Use the next page's import map on the imported script modules.
  • Find the best strategy to preload and replace all the CSS assets and HTML at the same time.
    • Keep an eye on CSS with incremental ids outside of the regions (see this issue).
  • Figure out if we need to whitelist all the compatible script modules.
  • Add a way to subscribe to virtual pageviews.
  • Make sure that client-side navigation is disabled when incompatible blocks are detected.

General enhancements

Core blocks (priority)

Core blocks (optional)

Bug fixes

Optional

@luisherranz luisherranz added [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. labels Nov 25, 2024
@sethrubenstein
Copy link
Contributor

Just an update that when we saw work on #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 #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.

@luisherranz
Copy link
Member Author

Wonderful, thanks Seth! 👏

I've added the Dialog block to the list 🙂

@sirreal
Copy link
Member

sirreal commented Nov 27, 2024

WordPress/wordpress-develop#7751 (.length support on server-processed directives) is ready for review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
None yet
Development

No branches or pull requests

3 participants