Skip to content

fix(cdk/scrolling): Prevents NaN being returned as firstVisibleIndex. #21505

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 1 commit into from
Jan 9, 2021

Conversation

Bjeaurn
Copy link
Contributor

@Bjeaurn Bjeaurn commented Jan 6, 2021

When firstVisibleIndex divides by zero, which can happen when the page is built and loaded dynamically; the NaN result will be used in other calculations.

This then throws off things like the newRange.start value also returning NaN, breaking the plugin.

@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 6, 2021
@Bjeaurn Bjeaurn changed the title fix: Prevents NaN being returned as firstVisibleIndex. fix (cdk/scrolling): Prevents NaN being returned as firstVisibleIndex. Jan 6, 2021
@Bjeaurn Bjeaurn changed the title fix (cdk/scrolling): Prevents NaN being returned as firstVisibleIndex. fix(cdk/scrolling): Prevents NaN being returned as firstVisibleIndex. Jan 6, 2021
When firstVisibleIndex divides by zero, which can happen when the page
is built and loaded dynamically; the NaN result will be used in other calculations.

This then throws off things like the `newRange.start` value also returning NaN, breaking the plugin.
@Bjeaurn Bjeaurn marked this pull request as ready for review January 6, 2021 15:26
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

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

LGTM

@crisbeto crisbeto added action: merge The PR is ready for merge by the caretaker 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 Jan 7, 2021
@annieyw annieyw merged commit 390afca into angular:master Jan 9, 2021
annieyw pushed a commit that referenced this pull request Jan 9, 2021
…#21505)

When firstVisibleIndex divides by zero, which can happen when the page
is built and loaded dynamically; the NaN result will be used in other calculations.

This then throws off things like the `newRange.start` value also returning NaN, breaking the plugin.

(cherry picked from commit 390afca)
wagnermaciel pushed a commit to wagnermaciel/components that referenced this pull request Jan 14, 2021
…angular#21505)

When firstVisibleIndex divides by zero, which can happen when the page
is built and loaded dynamically; the NaN result will be used in other calculations.

This then throws off things like the `newRange.start` value also returning NaN, breaking the plugin.
@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 Feb 9, 2021
@Bjeaurn Bjeaurn deleted the patch-1 branch February 1, 2024 11:02
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.

4 participants