Skip to content

fix(virtual-scroll): move views that are already attached instead of inserting #15359

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
Mar 1, 2019

Conversation

kara
Copy link
Contributor

@kara kara commented Mar 1, 2019

This PR contains the virtual scroll fix, but also some test updates and a commit from Jeremy to fix mat-button.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 1, 2019
With ivy, MatAnchor will inherit the host bindings of MatButton. The
`[disabled]` binding would then be an error since HTMLAnchorElement does
not have a `disabled` property. To work around this, we can simply use
the `disabled` attribute instead, which will always be reflected back
into the property when it exists.

Also add a missing `fixture.detectChanges()` to a test.
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 merged commit ce4b814 into angular:ivy-2019 Mar 1, 2019
@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 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants