Skip to content

perf(ripple): cache ClientRect between overlapping ripples #10206

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
Mar 6, 2018

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Mar 1, 2018

Avoids doing extra getBoundingClientRect calls when there are multiple active ripples. The cache is cleared once the last ripple is removed.

@crisbeto crisbeto requested a review from devversion as a code owner March 1, 2018 06:48
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 1, 2018
@crisbeto crisbeto force-pushed the ripple-rect-cache branch from 06e6be2 to 9070f2a Compare March 1, 2018 08:19
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 and removed pr: needs review labels Mar 1, 2018
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Mar 1, 2018
Avoids doing extra `getBoundingClientRect` calls when there are multiple active ripples. The cache is cleared once the last ripple is removed.
@crisbeto crisbeto force-pushed the ripple-rect-cache branch from 9070f2a to f221af4 Compare March 2, 2018 21:04
@jelbourn jelbourn merged commit 5c5f3b6 into angular:master Mar 6, 2018
@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 Sep 8, 2019
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 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