-
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
Zoom-out: scale should be stable function #60580
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.73 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.
I think this change makes sense to simplify the effect.
However, the zoom-out use case is passing a new function on every render, triggering the effect on every render as well.
I don't see the performance improvement part of this though. The effect looks like it's running the same amount of times on trunk vs this branch when toggling between zoom out mode. Could you point me to how you debugged this and saw the performance improvement?
@jeryj Apologies, I saw this while working on Prevent resizing from triggering re-renders, this would just be a preventative measure I guess. |
What?
In #59618, the iframe's scale prop was changed so a function can be passed. However, the zoom-out use case is passing a new function on every render, triggering the effect on every render as well.
Either we should:
I opted for the latter since the function seems like it's simple math (so fast) and this keeps the API simpler to use.
Why?
How?
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast