Skip to content

test(menu): fix test failures against Angular 4.2 #5168

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
Jul 27, 2017

Conversation

crisbeto
Copy link
Member

Fixes a couple of menu unit tests that were failing against Angular 4.2.2.

Fixes a couple of menu unit tests that were failing against Angular 4.2.2.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 16, 2017
@jelbourn
Copy link
Member

I was also investigating this now. Determining whether or not the root of this issue needs to be reverted in Angular core.

@crisbeto
Copy link
Member Author

crisbeto commented Jun 16, 2017

This seems to be the only place where it was happening, though. Perhaps we weren't doing it properly to begin with?

@jelbourn
Copy link
Member

I'm starting to think it's a bug because we import NoopAnimationModule and Angular's delegation to the animation driver for removal is not removing the element. Stepping through the animation code now.

@alexw10
Copy link

alexw10 commented Jun 21, 2017

Any update on this / on the path forward?

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

I sat down and looked at this with Matias and the conclusion was that it only worked by coincidence before 4.2 and that it should have always been doing this

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Jul 25, 2017
@andrewseguin andrewseguin merged commit b34b440 into angular:master Jul 27, 2017
@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 6, 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants