Skip to content

fix(google-maps): avoid re-initializing info window for same marker #19299

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
Jul 27, 2020

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented May 9, 2020

Currently if open is called multiple times for the same object, we keep re-initializing the info window. This can be seen in the dev app, because Chrome keeps logging warnings for some event listeners. These changes add a check that keeps the existing info window.

cc @mbehrlich

@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 May 9, 2020
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 9, 2020
Copy link
Collaborator

@mbehrlich mbehrlich left a comment

Choose a reason for hiding this comment

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

LGTM

@crisbeto crisbeto force-pushed the info-window-reinitialize branch from 4284b2e to 3b5c2bf Compare May 23, 2020 10:05
Currently if `open` is called multiple times for the same object, we keep re-initializing the info window. This can be seen in the dev app, because Chrome keeps logging warnings for some event listeners. These changes add a check that keeps the existing info window.
@crisbeto crisbeto force-pushed the info-window-reinitialize branch from 3b5c2bf to 36aec82 Compare July 3, 2020 21:02
@crisbeto
Copy link
Member Author

crisbeto commented Jul 3, 2020

Marking as LGTMed based on the review above.

@crisbeto crisbeto added lgtm action: merge The PR is ready for merge by the caretaker labels Jul 3, 2020
@jelbourn jelbourn merged commit 90f4d0e into angular:master Jul 27, 2020
jelbourn pushed a commit that referenced this pull request Jul 27, 2020
…19299)

Currently if `open` is called multiple times for the same object, we keep re-initializing the info window. This can be seen in the dev app, because Chrome keeps logging warnings for some event listeners. These changes add a check that keeps the existing info window.

(cherry picked from commit 90f4d0e)
@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 Aug 27, 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