Skip to content

[sidenav @alpha 9] Regression in styling: sidenav positioning is no longer fixed #1515

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

Closed
RoxKilly opened this issue Oct 18, 2016 · 4 comments · Fixed by #6712
Closed

[sidenav @alpha 9] Regression in styling: sidenav positioning is no longer fixed #1515

RoxKilly opened this issue Oct 18, 2016 · 4 comments · Fixed by #6712
Assignees
Labels
needs: discussion Further discussion with the team is needed before proceeding P2 The issue is important to a large percentage of users, with a workaround
Milestone

Comments

@RoxKilly
Copy link

RoxKilly commented Oct 18, 2016

Bug, feature request, or proposal:

Bug

What is the expected behavior?

md-sidenav should remain visible (fixed) even as the user scrolls down the md-sidenav-layout. This is how alpha 7 or 8 worked.

What is the current behavior?

alpha 9 has regressed. Now, when a user scrolls down to reveal more md-sidenav-layout content, md-sidenav goes off the page.

At top of the page; sidenav open:

1

After scrolling down; sidenav open:

2

What are the steps to reproduce?

  • open this plunker
  • scroll down the page
  • open the sidenav
  • the side menu is not visible.

What is the use-case or motivation for changing an existing behavior?

the md-sidenav typically shows a menu or other content that should be visible whenever the panel opens. Currently, the user experience is very poor: the user thinks the site is broken when she opens the sidenav and sees no content (scrolling up is required to reveal the content)

Which versions of Angular, Material, OS, browsers are affected?

Early alphas had this problem, but it was fixed probably around alpha 5. There has been a regression and I noticed the problem on alpha 9-3 on Firefox 49

@jelbourn jelbourn added the P2 The issue is important to a large percentage of users, with a workaround label Oct 18, 2016
@jelbourn
Copy link
Member

jelbourn commented Nov 1, 2016

@hansl might need some discussions about how we want scrolling to work with sidenav

@jelbourn jelbourn added this to the alpha.11 milestone Nov 1, 2016
@mischkl
Copy link

mischkl commented Jan 9, 2017

This is definitely an issue, and seems to be duplicated by #2416, #1793 and #2033 (and maybe more...). To be honest I'm not sure why anyone would want a sidebar where the navigation scrolls away simultaneously with the content - whereas the use case for keeping the sidebar fixed while scrolling the content seems universal. This is an issue which clearly has a lot of community demand and should be highly prioritized IMHO.

@PrazSam
Copy link

PrazSam commented Jan 25, 2017

I just fixed it following the accepted answer of this stackoverflow question . Have a look. This can be used as a workaround for the moment.

@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 7, 2019
@mmalerba mmalerba added the needs: discussion Further discussion with the team is needed before proceeding label Mar 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs: discussion Further discussion with the team is needed before proceeding P2 The issue is important to a large percentage of users, with a workaround
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants