Skip to content

fix(sidenav): remove margin from content instead of setting zero #11986

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
Jun 29, 2018

Conversation

jelbourn
Copy link
Member

@jelbourn jelbourn commented Jun 29, 2018

In SSR scenarios, the sidenav always gets 0 for DOM measurements,
causing it to always set a zero margin to the sidenav content. This
prevents an app from setting a custom margin so that the sidenav appears
correctly after SSR.

@jelbourn jelbourn requested a review from mmalerba as a code owner June 29, 2018 18:40
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 29, 2018
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

@josephperrott josephperrott 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 labels Jun 29, 2018
@jelbourn
Copy link
Member Author

cc @vikerman

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

In SSR scenarious, the sidenav always gets `0` for DOM measurements,
causing it to always set a zero margin to the sidenav content. This
prevents an app from setting a custom margin so that the sidenav appears
correctly after SSR.
@jelbourn jelbourn force-pushed the sidenav-no-zero-margin branch from 69f7cd1 to 1b86c32 Compare June 29, 2018 20:50
@josephperrott josephperrott merged commit 444fb38 into angular:master Jun 29, 2018
crisbeto added a commit to crisbeto/material2 that referenced this pull request Jul 4, 2018
Fixes the sidenav going into an infinite change detection loop when using the `autosize` option. Initially this was fixed in angular#11231, but it got reintroduced in angular#11986 where we started comparing `0` against `null` which always evaluates to true.

Fixes angular#11215.
crisbeto added a commit to crisbeto/material2 that referenced this pull request Jul 4, 2018
Fixes the sidenav going into an infinite change detection loop when using the `autosize` option. Initially this was fixed in angular#11231, but it got reintroduced in angular#11986 where we started comparing `0` against `null` which always evaluates to true.

Fixes angular#11215.
jelbourn pushed a commit that referenced this pull request Jul 11, 2018
Fixes the sidenav going into an infinite change detection loop when using the `autosize` option. Initially this was fixed in #11231, but it got reintroduced in #11986 where we started comparing `0` against `null` which always evaluates to true.

Fixes #11215.
jelbourn pushed a commit that referenced this pull request Jul 11, 2018
…12067)

Fixes the sidenav going into an infinite change detection loop when using the `autosize` option. Initially this was fixed in #11231, but it got reintroduced in #11986 where we started comparing `0` against `null` which always evaluates to true.

Fixes #11215.
victoriaaa234 pushed a commit that referenced this pull request Jul 25, 2018
…12067)

Fixes the sidenav going into an infinite change detection loop when using the `autosize` option. Initially this was fixed in #11231, but it got reintroduced in #11986 where we started comparing `0` against `null` which always evaluates to true.

Fixes #11215.
@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 9, 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