Skip to content

perf(focus-monitor): mark event listeners as passive #13532

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 2 commits into from
Oct 19, 2018

Conversation

devversion
Copy link
Member

@devversion devversion commented Oct 10, 2018

  • If a browser supports passive events, we should also mark the FocusMonitor global event listeners as passive, because browsers could technically make optimizations by knowing that these event listeners won't prevented and therefore can run non-blocking.

* If a browser supports passive events, we should also mark the `FocusMonitor` event listeners as passive, because browsers could technically make optimizations by knowing that _these_ event listeners won't prevented and therefore can run non-blocking.
@devversion devversion added perf This issue is related to performance target: patch This PR is targeted for the next patch release labels Oct 10, 2018
@devversion devversion requested a review from jelbourn as a code owner October 10, 2018 09:57
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 10, 2018
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

@devversion devversion added the action: merge The PR is ready for merge by the caretaker label Oct 10, 2018
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

@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 9, 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 perf This issue is related to performance target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants