[WIP] Block Supports: Try stabilizing common experimental block support flags #67018
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Depends on:
What?
Extends the approach to block support stabilization in #66918 to also stabilize shared/common experimental block support flags such as:
__experimentalSkipSerialization
__experimentalDefaultControls
Why?
These experimental flags have been around a long time and are extensively used throughout core blocks. It's time to stabilize them to increase confidence for extenders and better document what is possible.
How?
__experimentalSkipSerialization
within the filtered results due towp_should_skip_block_supports_serialization
in core only checking__experimentalSkipSerialization
. It will have to stick around in the Gutenberg filter until 6.8 is the minimum supported version.Next Steps
__experimentalSkipSerialization
and__experimentalDefaultControls
within Gutenberg's block supportsFuture follow-ups
Testing Instructions
Warning: This is likely going to need considerable testing!
Screenshots or screencast
There should be no visual differences in blocks between this PR and trunk. Any found are regressions.