Skip to content

fix(overlay): restore previous host element before attaching #17855

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
Jan 24, 2020

Conversation

dirkluijk
Copy link
Contributor

The first time when PositionStrategy.attach() is called, the overlay is already added to the DOM. However, after detaching and attaching again, it is not yet added to the DOM.

This PR changes the order and first restores the host element back, and then invokes the attach() method.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Dec 2, 2019
@jelbourn
Copy link
Member

jelbourn commented Dec 3, 2019

Is there a bug this is fixing? Are you able to add a unit test that captures the desired behavior?

@dirkluijk
Copy link
Contributor Author

Yes, I am trying to calculate the size of the overlay in my own PositionStrategy. However, after detaching and attaching, the size is 0,0 because it is still outside the DOM.

I will add a unit test for that.

@dirkluijk
Copy link
Contributor Author

I added the test. I double-checked it; without my fix it fails as expected.

@dirkluijk
Copy link
Contributor Author

Pushed the requested change.

Copy link
Member

@crisbeto crisbeto 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 added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent pr: lgtm action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release labels Dec 3, 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

@dirkluijk
Copy link
Contributor Author

Can this be merged?

@jelbourn jelbourn merged commit ee96e05 into angular:master Jan 24, 2020
yifange pushed a commit to yifange/components that referenced this pull request Jan 30, 2020
@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 Feb 24, 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