Skip to content
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

Ideas / Wishes for the SideNav #3717

Open
SvenBudak opened this issue Mar 22, 2017 · 8 comments
Open

Ideas / Wishes for the SideNav #3717

SvenBudak opened this issue Mar 22, 2017 · 8 comments
Labels
area: material/sidenav feature This issue represents a new feature or feature request rather than a bug or bug fix needs: discussion Further discussion with the team is needed before proceeding P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@SvenBudak
Copy link

SvenBudak commented Mar 22, 2017

I am a big fan of the Material2 Framework for Angular2. I Design now the Frontend of a couple of pages with this. But one thing is very frustrating for me and some of my friends. (We are just UX / Frontend Designers with very basic knowledge about Angular2)

We all need to ask every time programmers for making us the toggle function available in other components... This costs every time hours of time. isn't it possible, that you guys make a global Service for a important function like the SideNav? I mean nearly 100% of the people will need a global Toggle Function... I really really hope for any solution in future. :)

The other thing is, that we absolutely need a way, to use multiple SidenNvs from same directions. (align="end") In some projects, this is really needed, to improve the usability and user experience.

And the last wish is, a option to make the content area "sticky" when the Sidebar is open. It feels very strange, when i scroll the sidebar and the whole content scrolls to.

Sorry for my bad english. I hope very much, that you think about applying my Ideas / Wishes. :)

Very best regards!
BamiGorengo

@jelbourn jelbourn added discussion feature This issue represents a new feature or feature request rather than a bug or bug fix labels Apr 12, 2017
@wiwski
Copy link

wiwski commented Apr 12, 2017

Any workaround for the "sticky" sidenav?

@willshowell
Copy link
Contributor

@wiwski what worked for me was to examine the markup and css of material.angular.io/components. It's definitely possible and not too tricky, but requires some digging. It could use some documentation as it's likely the standard way of using sidenavs.

@BamiGorengo I personally disagree that a global toggle service should be Material's responsibility. It's pretty straightforward (not even 15 lines) to add a global service that exposes a toggle subject. Subscribe to that in your component and do mySidenav.toggle() each time the toggle subject emits.

@wiwski
Copy link

wiwski commented Apr 12, 2017

@willshowell I ended up setting html, body, md-sidenav-container { height: 100% } and it works just fine for me 👍

@axtho
Copy link

axtho commented Aug 8, 2017

+1 for some documentation (to save time digging)

@mackelito
Copy link

@willshowell perhaps the docs could mention this as a "Pro tip" and show some basic implementation code?

@axtho
Copy link

axtho commented Oct 10, 2017

Now that the fixedInViewport="true" feature is there the problem is (almost) solved. I have a request for one more option that is not implemented in the demo app: fixed sidenav that covers the header, but the scrolling content start underneath the header ... i.e. the header ist fixed also.

Now, you can achieve this by setting the toolbar on top of the sidenav-container. Works. But, what if I want the sidenav cover the entire top to bottom, and the main toolbar also fixed, with the scrolling content underneath. There seems to be no way to achieve this. @mmalerba

@mmalerba mmalerba added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label Nov 21, 2017
@mmalerba mmalerba added needs: discussion Further discussion with the team is needed before proceeding and removed discussion labels Mar 3, 2020
@angular-robot
Copy link
Contributor

angular-robot bot commented Feb 1, 2022

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

@angular-robot
Copy link
Contributor

angular-robot bot commented Feb 21, 2022

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: material/sidenav feature This issue represents a new feature or feature request rather than a bug or bug fix needs: discussion Further discussion with the team is needed before proceeding P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
8 participants