Skip to content

fix(overlay): error when rendering flexible overlay on the server #11072

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 1, 2018

Conversation

crisbeto
Copy link
Member

Adds a couple of checks to ensure that we, at least, don't throw an error if somebody tries to open a flexible overlay on the server. We can't handle it more gracefully, because we've got a lot of logic that depends on knowing the element dimensions.

Adds a couple of checks to ensure that we, at least, don't throw an error if somebody tries to open a flexible overlay on the server. We can't handle it more gracefully, because we've got a lot of logic that depends on knowing the element dimensions.
@crisbeto crisbeto requested a review from jelbourn as a code owner April 30, 2018 12:40
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 30, 2018
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 target: patch This PR is targeted for the next patch release and removed pr: needs review labels Apr 30, 2018
@josephperrott josephperrott merged commit 422d102 into angular:master May 1, 2018
@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 8, 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