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(youtube-player): avoid setInterval change detection when player is created #17894

Merged
merged 1 commit into from
Dec 6, 2019

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Dec 6, 2019

When we create a Player object for the youtube-player component, the YouTube API kicks off a 250ms setInterval which will trigger change detection even if the video is passive on the page. These change run the initialization code outside the NgZone so that doesn't happen.

…s created

When we create a `Player` object for the `youtube-player` component, the YouTube API kicks off a 250ms `setInterval` which will trigger change detection even if the video is passive on the page. These change run the initialization code outside the `NgZone` so that doesn't happen.
@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround pr: merge safe target: patch This PR is targeted for the next patch release labels Dec 6, 2019
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Dec 6, 2019
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

How did you even find this?

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Dec 6, 2019
@jelbourn jelbourn merged commit 27fae29 into angular:master Dec 6, 2019
@jelbourn
Copy link
Member

jelbourn commented Dec 6, 2019

It wouldn't be a bad idea to also initialize the google maps stuff outside the zone while we're at it

@crisbeto
Copy link
Member Author

crisbeto commented Dec 6, 2019

ops, I forgot to reference the proper issue. Credit goes to @ukyo for finding it. #17882

@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 Jan 6, 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 P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants