Skip to content

test: fix listbox spec failing due to keyboard event helper update #20060

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

devversion
Copy link
Member

We landed two PRs. One that added a new usage of createKeyboardEvent
and another one that changed the signature of createKeyboardEvent.

This meant that the first PR adding the new instance does not account
for the new function signature and CI/build is failing.

We landed two PRs. One that added a new usage of `createKeyboardEvent`
and another one that changed the signature of `createKeyboardEvent`.

This meant that the first PR adding the new instance does not account
for the new function signature and CI/build is failing.
@devversion devversion added P2 The issue is important to a large percentage of users, with a workaround merge safe target: patch This PR is targeted for the next patch release labels Jul 21, 2020
@devversion devversion requested a review from jelbourn as a code owner July 21, 2020 19:29
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jul 21, 2020
Copy link
Contributor

@wagnermaciel wagnermaciel left a comment

Choose a reason for hiding this comment

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

LGTM

@wagnermaciel wagnermaciel added lgtm action: merge The PR is ready for merge by the caretaker labels Jul 21, 2020
@wagnermaciel wagnermaciel merged commit e16997c into angular:master Jul 21, 2020
wagnermaciel pushed a commit that referenced this pull request Jul 21, 2020
…20060)

We landed two PRs. One that added a new usage of `createKeyboardEvent`
and another one that changed the signature of `createKeyboardEvent`.

This meant that the first PR adding the new instance does not account
for the new function signature and CI/build is failing.

(cherry picked from commit e16997c)
@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 Aug 21, 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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants