-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Some IE11 cleanups accidentally landed in 12.2.x #23736
Comments
Updating this issue to cover all IE11 cleanups that accidentally landed in the
We should revert this fix on the |
@Wisdomb33r I don't have access to a device with IE11 at this moment- can you provide a pointer to the block of code where the problematic |
…ar#23562)" This reverts commit 6b71169. Reverts this badge fix because it relies on a querySelector API that is not supported in IE11. Related to angular#23736
@crisbeto did some digging and determined that issue related to datepicker here comes from a missing polyfill
Closing this since the other issue (badge) has been reverted and should be back to normal in the next patch release. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Reproduction
Steps to reproduce:
It seems to be because of this line
const badges = this._elementRef.nativeElement.querySelectorAll(
:scope > .${BADGE_CONTENT_CLASS});
located in this method
_clearExistingBadges
In the badge component
Expected Behavior
We should see the badge correctly even in IE
Actual Behavior
The badge is not displayed and we have a syntax error in the IE console
Environment
The text was updated successfully, but these errors were encountered: