Skip to content

virtual-scroll: switch back to markForCheck since detectChanges #12329

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 3 commits into from
Jul 24, 2018

Conversation

mmalerba
Copy link
Contributor

breaks viewports that are inside an OnPush component.

Fixes issue introduced by #12158

@mmalerba mmalerba requested review from amcdnl, jelbourn and crisbeto July 23, 2018 17:07
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jul 23, 2018
@mmalerba mmalerba added pr: merge safe target: patch This PR is targeted for the next patch release labels Jul 23, 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

@crisbeto crisbeto added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jul 23, 2018
@@ -315,7 +311,7 @@ export class CdkVirtualScrollViewport implements OnInit, OnDestroy {
this._isChangeDetectionPending = false;

// Apply changes to Angular bindings.
this._ngZone.run(() => this._changeDetectorRef.detectChanges());
this._ngZone.run(() => this._changeDetectorRef.markForCheck());
Copy link
Member

Choose a reason for hiding this comment

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

Add a comment here that explains the context around using markForCheck so that someone else down the line doesn't try to switch to detectChanges again?

@mmalerba mmalerba merged commit e67fd7b into angular:master Jul 24, 2018
mmalerba added a commit that referenced this pull request Jul 30, 2018
…12329)

breaks viewports that are inside an `OnPush` component.

Fixes issue introduced by #12158
@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 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