Skip to content

Conversation

@crisbeto
Copy link
Member

@crisbeto crisbeto commented Mar 8, 2020

We have a code path where we call contains either on a DOM node or the Document, but on IE the Document doesn't support contains which results in an error. These changes add a workaround where we use the documentElement instead.

We have a code path where we call `contains` either on a DOM node or the `Document`, but on IE the `Document` doesn't support `contains` which results in an error. These changes add a workaround where we use the `documentElement` instead.
@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 Mar 8, 2020
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 8, 2020
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added lgtm action: merge The PR is ready for merge by the caretaker labels Mar 9, 2020
@andrewseguin andrewseguin merged commit 531ea7c into angular:master Mar 12, 2020
andrewseguin pushed a commit that referenced this pull request Mar 12, 2020
)

We have a code path where we call `contains` either on a DOM node or the `Document`, but on IE the `Document` doesn't support `contains` which results in an error. These changes add a workaround where we use the `documentElement` instead.

(cherry picked from commit 531ea7c)
@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 Apr 12, 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.

4 participants