-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Editor: make VisualEditor a stacking context #62681
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: +16 B (0%) Total Size: 1.76 MB
ℹ️ View Unchanged
|
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.
This PR is working as expected. Also, as far as I tested, there are no other issues caused by this PR.
Before
After
However, the next release this PR will be backported is RC version, and to be on the safe side, I would like to ask for a second review by people who are knowledgeable in this area 🙏
@@ -3,6 +3,8 @@ | |||
height: 100%; | |||
display: block; | |||
background-color: $gray-300; | |||
// Make this a stacking context to contain the z-index of children elements. | |||
isolation: isolate; |
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.
😬 I just learned about this
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.
Same 😅
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.
😬 I just learned about this
And yet you used the property here 😆
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.
I know I know, that's where I saw it first. I copied it form the View Transition Guide (by Google) to reset cross-shadow transitions :P
Seems ok to me but I wonder what impact this change can have. (other z-index related impact) |
Personally, I think this issue is less serious. Would it be better to test it only on Gutenberg for now and not backport it to WP 6.6? |
I’m all for making haste slowly. The property could have been on the
They are all probably expected to be no higher than the visual editor itself and seem to work as expected. Any popover launched from those is out in the fallback container as are any other popovers I've found in the interface so can’t be affected by this change. |
@stokesman I think it would be better to merge this PR without the backport label just to be safe. What do you think? |
It’s fine by me. Is there a chance to still fix the issue in 6.6? If not by backporting this later then perhaps a PR which fixes it by changing z-index? I know the issue isn’t critical but it’d be nice have it done. |
Sure it's fine, but needs to be merged asap, we're cherrypicking rn |
826b008
to
8937f9d
Compare
It seemed like GitHub Actions had stopped, so I rebased it to get it running again. |
Flaky tests detected in 8937f9d. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/9660133699
|
Co-authored-by: stokesman <presstoke@git.wordpress.org> Co-authored-by: t-hamano <wildworks@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org> Co-authored-by: ellatrix <ellatrix@git.wordpress.org>
I just cherry-picked this PR to the wp/6.6 branch to get it included in the next release: 349a36d |
@stokesman Maybe this PR caused an issue with popovers. Is there a way to fix this? Please see #62998 |
What?
A change to
VisualEditor
so it contains z-indexes of children within it (as a stacking context)Why?
To fix #62639, in which it’s noted that the block toolbar is not actually underneath the editor header and so the header’s shadow disappears behind it.
How?
Add
isolation: isolate
to the component’s root element.Testing Instructions