-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Use standard CSS rules to resize emoticons #29276
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@lorumic Maybe we can do both here? Do you mind testing on both?
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.
The problem is that if you do both, both get applied on FF 133, resulting in the issue that was reported: 0.5 from
zoomand 0.5 fromtransform: scaleresults in a final 0.25 size.I think the takeaway here is that the usage of
zoomshould not be mixed with that oftransform: scale. You could usezoomonly, but that would probably affect your browser compatibility: scale vs zoom.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.
Ah thank you. I acknowledge that my knowledge of css is subpar, thus I'm seeking others to help. I'm just throwing a few ideas.
Perhaps we can use
@supports? Again, this may not work as I don't spend much time on web css (I'm more of a mobile engineer here at MM).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 is a good idea, but it should be the other way around, as
zoomis the less-supported property. :)I have just updated the code to use
zoomwhenever supported (which means "always" in Chrome, where the blurriness problem originally occurred, because Chrome supports it since version 1), and fall back totransform: scalewhen unsupported (e.g. FF versions before 126).Can you maybe have another look @rahimrahman?
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.
Smart, totally see your reasoning of reversing. Of course, my example would have cause blurriness on Chrome and totally not fixing the problem. 😏
Do you have a screenshot of Chrome which shows no blurriness and another on Firefox that shows the icon is the correct size? Visual representation helps a lot, especially for other reviewers.
Thanks for working to solve this even at small scale (pun intended!). I appreciate helping me understand the diff between zoom and scale. Something I have not encountered before (again as a mobile dev, I don't spend a lot of time 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.
Just re-read that you're on Linux. Let me check on mine, or we can get one of our QAs to verify.