You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@elalish I finally got to test this; looks like it's nearly fixed!
From zooming around I can see that now all resolutions stay at exactly the same pixel values but 90% and 110% still jump by a pixel, reducing clarity. This means that almost every zoom looks super crisp and sharp but the common values of 90% and 110% are still somewhat blurry.
Without the PR, all values would be slightly different and thus everything was slightly blurry at all but 100% values. Now, only those two jump by a pixel.
(the relevant part is that in the lower right, the <canvas width=518 height=1121> jumps to <canvas width=519 height=1122> when zooming at 90% and 110%.
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
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.
Fixes #1503
Well, I can't repro the issue so I can't be sure, but this seems a likely fix. @hybridherbst Can you verify this fix before I merge?