Skip to content

refactor(autocomplete): rework cases not using document token #15366

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
May 13, 2019

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Mar 2, 2019

Fixes a couple of places that were referring to the global document variable, rather than using the token. These could potentially throw on the server, if a code path somehow hit them.

@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Mar 2, 2019
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 2, 2019
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 pr: lgtm action: merge The PR is ready for merge by the caretaker labels Apr 2, 2019
@mmalerba mmalerba added aaa and removed aaa labels Apr 25, 2019
@jelbourn
Copy link
Member

@crisbeto this passes presubmit, just needs a rebase

Fixes a couple of places that were referring to the global `document` variable, rather than using the token. These could potentially throw on the server, if a code path somehow hit them.
@crisbeto crisbeto force-pushed the autocomplete-document-token branch from bd9500d to 36a2fbf Compare May 13, 2019 16:19
@crisbeto
Copy link
Member Author

Rebased.

@jelbourn jelbourn merged commit 07e8028 into angular:master May 13, 2019
RudolfFrederiksen pushed a commit to RudolfFrederiksen/material2 that referenced this pull request Jun 21, 2019
…r#15366)

Fixes a couple of places that were referring to the global `document` variable, rather than using the token. These could potentially throw on the server, if a code path somehow hit them.
@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 10, 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 cla: yes PR author has agreed to Google's Contributor License Agreement 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