You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
π Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @karthikeya-io! In case you missed it, we'd love to have you join us in our Slack community.
If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.
If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
The reason will be displayed to describe this comment to others. Learn more.
This is great! Thanks for working on it. Iβve experimented with some alternatives and it does seem like leveraging a MutationObserver is the best bet.
Iβve tested this and didnβt find any problems. I think it might not be necessary to observe the class attribute and just the style may suffice but I donβt think itβs likely to be critical for performance and may be helpful in some less common cases.
Iβd be okay with this landing as is but I have a few suggestions.
* Fix: Space visualizer showing previous value
* Refactor: replace useLayoutEffect with useEffect and remove unnecessary value from deps
Co-authored-by: karthikeya-io <karthikeya01@git.wordpress.org>
Co-authored-by: stokesman <presstoke@git.wordpress.org>
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.
What?
Part of #63191
Why?
Fixes the issue that Margin and Padding visualizer shows the previous value. This issue doesn't occur in Safari but occurs in Chromium based browsers.
Related PR #59227
How?
Use
MutationObserver
to observe the changes in block.Testing Instructions
Testing Instructions for Keyboard
Same
Screenshots or screencast
space-visualizer-before.mov
space-visualizer-after.mov