fix: rtl scroll converter test asserting incorrect values #6859
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.
Pull Request
π Description
Changes the
invertedGetRtlScrollConverter returns correct value
test to pass when any value < 0 is returned.π« Issues
This PR reverts #6857.
π©βπ» Reviewer Notes
The behavior seems to be related to this Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1324251
It's something called "zoom for DSF" on MacOS, which leads to inaccurate value reporting:
1
0.5
0
0
So while I do still think that screen DPI is partly to blame for Chrome returning
0.5
, it seems that settingscrollLeft
to1
when in rtl mode and receiving anything other than0
is a bug.β Checklist
General
$ yarn change