Skip to content

fix(cdk/testing): Make harnesses click on the center of the element by default #19212

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 4 commits into from
May 1, 2020

Conversation

mmalerba
Copy link
Contributor

@mmalerba mmalerba commented Apr 29, 2020

This is Protractor's default behavior. Prior to this PR we had been
clicking the top-left corner, but that didn't trigger the click event in
Protractor.

fixes #19002

@mmalerba mmalerba added P2 The issue is important to a large percentage of users, with a workaround regression This issue is related to a regression labels Apr 29, 2020
@mmalerba mmalerba requested a review from jelbourn April 29, 2020 21:40
@mmalerba mmalerba requested a review from devversion as a code owner April 29, 2020 21:40
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 29, 2020
@jelbourn
Copy link
Member

jelbourn commented Apr 29, 2020

Could you also expand the commit message with more context about the fix?

@jelbourn jelbourn added the target: patch This PR is targeted for the next patch release label Apr 30, 2020
…y default

This is Protractor's default behavior. Prior to this PR we had been
clicking the top-left corner, but that didn't trigger the click event in
Protractor.
@mmalerba mmalerba changed the title fix(cdk/testing): Make harnesses click on relative coord 1,1 - not 0,0 fix(cdk/testing): Make harnesses click on the center of the element by default Apr 30, 2020
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

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

LGTM. One optional nit and API goldens seem to fail.

@mmalerba mmalerba requested a review from a team as a code owner April 30, 2020 21:04
@mmalerba
Copy link
Contributor Author

Yeah this is technically breaking, since I'm not allowing you to pass only relativeX anymore, you must pass both or none

@jelbourn jelbourn added the action: merge The PR is ready for merge by the caretaker label Apr 30, 2020
@jelbourn jelbourn merged commit a9ca95e into angular:master May 1, 2020
jelbourn pushed a commit that referenced this pull request May 1, 2020
…y default (#19212)

* fix(cdk/testing): Make harnesses click on the center of the element by default

This is Protractor's default behavior. Prior to this PR we had been
clicking the top-left corner, but that didn't trigger the click event in
Protractor.

* address feedback

* clarifying comment

* update api goldens
@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 Jun 1, 2020
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 P2 The issue is important to a large percentage of users, with a workaround regression This issue is related to a regression target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug(MatButtonHarness): Button events not triggering on Protractor environemnt
5 participants