-
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
Command Center: Fix a style glitch on Safari #50138
Conversation
Should this live as an inline style, or in a separate CSS file? Asking mostly out of curiosity as my instinct would've been the latter, but curious to your reasons. Can you try the more standardized |
Size Change: +36 B (0%) Total Size: 1.37 MB
ℹ️ View Unchanged
|
Yeah no preference here :) I'll make your suggested updates. |
@@ -36,6 +36,9 @@ | |||
} | |||
|
|||
.commands-command-menu__container { | |||
// the style here is a hack to force safari to repaint to avoid a style glitch |
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 this is terribly nitpicky, but do we have a standard for code comments? I normally use sentence capitalization and end with a period 🙈
It's not a strong opinion, we just have a mix of styles.
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.
Flaky tests detected in 426af33. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4820493059
|
Let's get this in :) |
Related #48457
What?
In Safari, as you type in the command center (cmd+k) you can see some visual glitches in the modal. I'm thinking this is probably a Safari bug but I wasn't able to find the root cause. The current PR solves the issue by forcing a browser repaint on render (using the transform style).
Testing Instructions