Add support for custom spacing in core #951
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
I've also prepared the corresponding changes for Gutenberg WordPress/gutenberg#28548 |
82 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
See track ticket https://core.trac.wordpress.org/ticket/51760
As per WordPress/gutenberg#25788 the
experimental-custom-spacingwas marked stable and themes can now add support for it viaadd_theme_support('custom-spacing'). This PR adds support for it in core.Test instructions
For this to work, it needs WordPress/gutenberg#28548 to be part of Gutenberg 9.9 and the packages to be released and merged in WordPress core.
When that's done, the instructions below should be reproducible:
custom-spacing.