Skip to content

build: fix autocomplete test failures on ios #10442

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

Conversation

crisbeto
Copy link
Member

Fixes a couple of positioning unit test failures on iOS Safari after the switch to the flexible connected position. The issue appears to be a combination of us stubbing out the ScrollDispatcher for all tests which means that if one test scrolls the window down, any subsequent tests won't pick up the scroll position correctly, as well as having a test that scrolls the page down, but doesn't reset it. These changes:

  • Reset the position back to the top after the scrolling test is done.
  • Rework the tests to only stub out the ScrollDispatcher in the two tests where it's relevant.

Fixes a couple of positioning unit test failures on iOS Safari after the switch to the flexible connected position. The issue appears to be a combination of us stubbing out the `ScrollDispatcher` for all tests which means that if one test scrolls the window down, any subsequent tests won't pick up the scroll position correctly, as well as having a test that scrolls the page down, but doesn't reset it. These changes:

* Reset the position back to the top after the scrolling test is done.
* Rework the tests to only stub out the `ScrollDispatcher` in the two tests where it's relevant.
@crisbeto crisbeto added the in progress This issue is currently in progress label Mar 16, 2018
@crisbeto crisbeto self-assigned this Mar 16, 2018
@crisbeto crisbeto requested a review from kara as a code owner March 16, 2018 05:12
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 16, 2018
@crisbeto crisbeto changed the title wip: fix autocomplete test failures on ios build: fix autocomplete test failures on ios Mar 16, 2018
@crisbeto crisbeto assigned josephperrott and unassigned crisbeto Mar 16, 2018
@crisbeto crisbeto added pr: needs review and removed in progress This issue is currently in progress labels Mar 16, 2018
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

@josephperrott josephperrott added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Mar 16, 2018
@mmalerba mmalerba merged commit c28549d into angular:master Mar 16, 2018
josephperrott pushed a commit to josephperrott/components that referenced this pull request Mar 19, 2018
Fixes a couple of positioning unit test failures on iOS Safari after the switch to the flexible connected position. The issue appears to be a combination of us stubbing out the `ScrollDispatcher` for all tests which means that if one test scrolls the window down, any subsequent tests won't pick up the scroll position correctly, as well as having a test that scrolls the page down, but doesn't reset it. These changes:

* Reset the position back to the top after the scrolling test is done.
* Rework the tests to only stub out the `ScrollDispatcher` in the two tests where it's relevant.
@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 8, 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.

4 participants