-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
DocumentBar: Fix browser warning error #59193
Conversation
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: +7 B (0%) Total Size: 1.7 MB
ℹ️ View Unchanged
|
Flaky tests detected in 24319ea. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7969281254
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice spotting. 🍺
Works for me!
@ramonjd Thanks for the review! |
There's probably a bug with If you want to avoid the extra CSS you could try |
cc @mirka and @andrewhayward since Marco's currently on leave. |
Thanks for flagging! Fix in #59416. |
Related to #58656
What?
This PR fixes the browser warning error when the canvas is the edit mode.
7b4520c33ebf97f68bc5da94b940a8d7.mp4
Why?
The error logged in the browser console is as follows:
Details
It seems that for some reason the DOM element is given an incorrect prop called
isColumn
. Using React Dev Tools, you can see that theView
component, which is rendered as a div element, is given a prop calledisColumn
.How?
To be honest, I haven't been able to pinpoint the root cause, but in most cases it seems that the
motion.div
itself is being used as a component instead of passing itas
prop. In fact, this approach solved the console error.Testing Instructions