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(connected-position-strategy): position change event not emitting for fallback positions #5978

Merged

Conversation

crisbeto
Copy link
Member

  • Fixes the onPositionChange event from the ConnectedPositionStrategy not emitting if the strategy picks one of the fallback positions.
  • Fixes the autocomplete panel not having the proper offset when it is in the above position. This was tightly-coupled to the onPositionChange not firing.
  • Fixes a couple of tests that were nested in another test, causing them not to be executed. I've removed one of the tests since it was also duplicated with one above. This seems to have been the result of a faulty conflict resolution.

…for fallback positions

* Fixes the `onPositionChange` event from the `ConnectedPositionStrategy` not emitting if the strategy picks one of the fallback positions.
* Fixes the autocomplete panel not having the proper offset when it is in the `above` position. This was tightly-coupled to the `onPositionChange` not firing.
* Fixes a couple of tests that were nested in another test, causing them not to be executed. I've removed one of the tests since it was also duplicated with one above. This seems to have been the result of a faulty conflict resolution.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jul 23, 2017
@crisbeto
Copy link
Member Author

crisbeto commented Jul 23, 2017

@jelbourn, I have a hunch that the flakes we were seeing when we started randomizing the tests were due to the two tests that were nested in another test. What I think was happening was that they would eventually get executed, if the randomization was just right, causing one of them to fail. The failing one also had the assertions from a completely different test due to a faulty rebase.

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, nice

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Jul 24, 2017
@kara kara removed their assignment Jul 24, 2017
@andrewseguin andrewseguin merged commit 63505dc 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