[wp-trac] [WordPress Trac] #61185: Interactivity API: Move directive processing to `WP_Block` class
WordPress Trac
noreply at wordpress.org
Mon May 13 16:25:17 UTC 2024
#61185: Interactivity API: Move directive processing to `WP_Block` class
-------------------------------+---------------------
Reporter: gziolo | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: 6.6
Component: Interactivity API | Version: 6.5
Severity: normal | Resolution:
Keywords: has-patch | Focuses:
-------------------------------+---------------------
Comment (by cbravobernal):
Replying to [comment:2 gziolo]:
> I now see that it might have some implications on e2e tests in the
Gutenberg plugin where
`wp_interactivity_process_directives_of_interactive_blocks` gets removed:
>
>
https://github.com/WordPress/gutenberg/blob/f69bd7af630194b459c7de1cba7627a39715e5fa/packages
/e2e-tests/plugins/interactive-blocks.php#L32-L36
>
> We would need to figure out an alternative way to disable directive
processing. It would be valuable to have a formal way to do it anyway as
the need clearly exists. Any ideas how that could be done?
>
Those tests are testing that the runtime is still working, while the SSR
is not. I don't consider a real need to be able to disable SSR, but it
would be a good addition.
We could add a filter (seems pretty straightforward) or use
`wp_interactivity_config`.
https://github.com/gziolo/wordpress-
develop/blob/ff14587d0885caaaf620c4bc5c7951b1a7f388c9/src/wp-includes
/interactivity-api/interactivity-api.php#L77
--
Ticket URL: <https://core.trac.wordpress.org/ticket/61185#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list