Skip to content

fix(form-field): error in older versions of edge #19698

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 1 commit into from
Jun 29, 2020

Conversation

crisbeto
Copy link
Member

Some older versions of Edge will throw an error due to the way we were iterating over an HTMLCollection. This is actually something that TS throws a compilation error for, but we didn't catch it, because the variable was being inferred as any.

Fixes #17810.

Some older versions of Edge will throw an error due to the way we were iterating over an `HTMLCollection`. This is actually something that TS throws a compilation error for, but we didn't catch it, because the variable was being inferred as `any`.

Fixes angular#17810.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release labels Jun 19, 2020
@crisbeto crisbeto requested a review from mmalerba as a code owner June 19, 2020 18:30
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 19, 2020
Copy link
Contributor

@mmalerba mmalerba left a comment

Choose a reason for hiding this comment

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

LGTM

@mmalerba mmalerba added lgtm action: merge The PR is ready for merge by the caretaker labels Jun 19, 2020
@jelbourn jelbourn merged commit e1bfb92 into angular:master Jun 29, 2020
jelbourn pushed a commit that referenced this pull request Jun 29, 2020
Some older versions of Edge will throw an error due to the way we were iterating over an `HTMLCollection`. This is actually something that TS throws a compilation error for, but we didn't catch it, because the variable was being inferred as `any`.

Fixes #17810.
@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 Jul 30, 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 P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

mat-form-field with appearance set to outline throws type error on older browsers
4 participants