Skip to content

fix(router): IE 11 bug can break URL unification when comparing objects - #30393

Closed
jasonaden wants to merge 1 commit into
angular:masterfrom
jasonaden:fix_IE11_url_unification
Closed

jasonaden wants to merge 1 commit into
angular:masterfrom
jasonaden:fix_IE11_url_unification

Conversation

@jasonaden

Copy link
Copy Markdown
Contributor

This PR fixes an issue where IE 11 can return undefined in with an Object.keys call. Solution is to add a runtime check on the value. Based on the types being passed, this shouldn't be necessary, but is needed only for IE 11. Unit test doesn't work for this PR because it can't be replicated easily.

@jasonaden
jasonaden requested a review from a team May 10, 2019 15:55
@ngbot ngbot Bot added this to the needsTriage milestone May 10, 2019
This PR fixes an issue where IE 11 can return `undefined` in with an `Object.keys` call. Solution is to add a runtime check on the value. Based on the types being passed, this shouldn't be necessary, but is needed only for IE 11. Unit test doesn't work for this PR because it can't be replicated easily.
@jasonaden
jasonaden force-pushed the fix_IE11_url_unification branch from 719312c to f311bd7 Compare May 10, 2019 21:57
@jasonaden jasonaden added action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release type: bug/fix labels May 10, 2019
@alxhub

alxhub commented May 13, 2019

Copy link
Copy Markdown
Member

Presubmit

alxhub pushed a commit that referenced this pull request May 13, 2019
…ts (#30393)

This PR fixes an issue where IE 11 can return `undefined` in with an `Object.keys` call. Solution is to add a runtime check on the value. Based on the types being passed, this shouldn't be necessary, but is needed only for IE 11. Unit test doesn't work for this PR because it can't be replicated easily.

PR Close #30393
@alxhub alxhub closed this in 197584d May 13, 2019
@thorn0

thorn0 commented May 14, 2019

Copy link
Copy Markdown
Contributor

Where can I learn more about this IE bug? I can't find anything about it anywhere.

jasonaden added a commit to jasonaden/angular that referenced this pull request May 14, 2019
…on when comparing objects

PR angular#30393 corrected behavior where Object.keys sometimes returns an `undefined` value. However, the types didn't reflect this in the code. That fix actually missed one value that could return `undefined`. This PR corrects this by casting the types to what they can be in IE 11. This ensures the code behaves as it should when this edge case comes up.
jasonaden added a commit that referenced this pull request May 15, 2019
…on when comparing objects (#30464)

PR #30393 corrected behavior where Object.keys sometimes returns an `undefined` value. However, the types didn't reflect this in the code. That fix actually missed one value that could return `undefined`. This PR corrects this by casting the types to what they can be in IE 11. This ensures the code behaves as it should when this edge case comes up.

PR Close #30464
jasonaden added a commit that referenced this pull request May 15, 2019
…on when comparing objects (#30464)

PR #30393 corrected behavior where Object.keys sometimes returns an `undefined` value. However, the types didn't reflect this in the code. That fix actually missed one value that could return `undefined`. This PR corrects this by casting the types to what they can be in IE 11. This ensures the code behaves as it should when this edge case comes up.

PR Close #30464
BioPhoton pushed a commit to BioPhoton/angular that referenced this pull request May 21, 2019
…ts (angular#30393)

This PR fixes an issue where IE 11 can return `undefined` in with an `Object.keys` call. Solution is to add a runtime check on the value. Based on the types being passed, this shouldn't be necessary, but is needed only for IE 11. Unit test doesn't work for this PR because it can't be replicated easily.

PR Close angular#30393
BioPhoton pushed a commit to BioPhoton/angular that referenced this pull request May 21, 2019
…on when comparing objects (angular#30464)

PR angular#30393 corrected behavior where Object.keys sometimes returns an `undefined` value. However, the types didn't reflect this in the code. That fix actually missed one value that could return `undefined`. This PR corrects this by casting the types to what they can be in IE 11. This ensures the code behaves as it should when this edge case comes up.

PR Close angular#30464
@angular-automatic-lock-bot

Copy link
Copy Markdown

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 15, 2019
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 area: router cla: yes target: patch This PR is targeted for the next patch release type: bug/fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants