Skip to content
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

fix(platform): RTL scrolling behavior detection not using cached value in some cases #18389

Merged
merged 1 commit into from
Feb 20, 2020

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Feb 4, 2020

The getRtlScrollAxisType function caches its value so that we don't have to hit the DOM multiple times to detect the behavior. The problem is that when it reads the cached value, it does a simple falsy check which will also be true when we've resolved the value to NORMAL (which is 0).

…e in some cases

The `getRtlScrollAxisType` function caches its value so that we don't have to hit the DOM multiple times to detect the behavior. The problem is that when it reads the cached value, it does a simple falsy check which will also be true when we've resolved the value to `NORMAL`.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release labels Feb 4, 2020
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Feb 4, 2020
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Feb 4, 2020
@andrewseguin andrewseguin merged commit 633e4c2 into angular:master Feb 20, 2020
andrewseguin pushed a commit that referenced this pull request Feb 20, 2020
…e in some cases (#18389)

The `getRtlScrollAxisType` function caches its value so that we don't have to hit the DOM multiple times to detect the behavior. The problem is that when it reads the cached value, it does a simple falsy check which will also be true when we've resolved the value to `NORMAL`.

(cherry picked from commit 633e4c2)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Mar 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants