Skip to content

refactor(cdk/testing): switch to event constructor for creating fake events #23394

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

Conversation

devversion
Copy link
Member

Switches from the legacy init<..>Event calls to the Event constructors
given that IE11 no longer is supported.

@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 18, 2021
@devversion devversion force-pushed the refactor/switch-to-event-constructors-for-fake-events branch 4 times, most recently from d9a7880 to ef01eb0 Compare August 18, 2021 15:56
@devversion
Copy link
Member Author

Test failures for cdk/a11y seem to be unrelated. see #23395

@devversion devversion added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: major This PR is targeted for the next major release labels Aug 18, 2021
@devversion devversion marked this pull request as ready for review August 18, 2021 16:05
@devversion devversion requested a review from jelbourn as a code owner August 18, 2021 16:05
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

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

LGTM

…events

Switches from the legacy `init<..>Event` calls to the Event constructors
given that IE11 no longer is supported.
@devversion devversion force-pushed the refactor/switch-to-event-constructors-for-fake-events branch from ef01eb0 to b014380 Compare August 18, 2021 17:31
@devversion devversion added action: merge The PR is ready for merge by the caretaker merge: preserve commits When the PR is merged, a rebase and merge should be performed labels Aug 18, 2021
The fake `TouchEvent` being created by test harnesses for the
TestBed harness environment currently set an id for a `Touch`
of the fake event. The `Touch` currently incorrectly sets the
unique touch id to a field named `id`, while it should be `identifier`.
@devversion devversion force-pushed the refactor/switch-to-event-constructors-for-fake-events branch from b014380 to 366c303 Compare August 18, 2021 18:14
@amysorto amysorto merged commit 692ebaf into angular:master Aug 20, 2021
@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 20, 2021
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 merge: preserve commits When the PR is merged, a rebase and merge should be performed P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants