-
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
Site Editor: add units to avoid console warning #64810
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: -2 B (0%) Total Size: 1.77 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.
Good catch 🚀
Should we add an inline comment to avoid regressions? A best practice is to omit units when using |
I’d love if this type of issue could be avoided entirely. I tried a comment but wasn’t satisfied it will help much generally and a regression of this particular instance isn’t too worrisome I think. |
Co-authored-by: t-hamano <wildworks@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
What?
A fix to avoid a browser console warning that looks to have came about with #63986.
Why?
It’s easy to avoid.
How?
Adds units to the keyframe values.
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast
The warning as seen on trunk
edit-site-site-icon-console-warning.mp4