Skip to content

Feature Request: Close Sidenav menu on Responsive when using gesture slide/swipe left. #13001

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
AsantosCandor opened this issue Sep 6, 2018 · 4 comments
Assignees
Labels
area: material/sidenav feature This issue represents a new feature or feature request rather than a bug or bug fix P5 The team acknowledges the request but does not plan to address it, it remains open for discussion

Comments

@AsantosCandor
Copy link

AsantosCandor commented Sep 6, 2018

Bug, feature request, or proposal: Feature Request

What is the expected behavior?

Regarding the material sidenav, right now the current behavior is that we can close the drawer either calling the drawer.close or when backdropClicking. In Responsive mode thre should be a sliding out from the side-nav just like in the GMAIL application. We can either close by backdrop clicking, clicking outside or sliding the menu out.

What is the current behavior?

Regarding the material sidenav, right now the current behavior is that we can close the drawer either calling the drawer.close or when backdropClicking/click outside.

What are the steps to reproduce?

This is one of the examples provided on the angular material page.

https://stackblitz.com/angular/pdxjaplpmav?file=app%2Fsidenav-disable-close-example.html

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

When building the top-nav menu, or sidenav container that we use as the top-navigator for desktop, and the sidenav for responsive/mobile we have available the clickOutside close, but sliding out of the menu should also be available since it provides a better user experience.

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

Angular 6, Material 6.4.7

Is there anything else we should know?

If anyone has a simple solution for this I am open to it. Since right now the only solution I am getting is using hammer.js for gestures detection and close the drawer.

@josephperrott josephperrott added feature This issue represents a new feature or feature request rather than a bug or bug fix P5 The team acknowledges the request but does not plan to address it, it remains open for discussion labels Sep 7, 2018
@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 22, 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.

@crisbeto
Copy link
Member

Sounds like a duplicate of #5712.

@crisbeto crisbeto self-assigned this Jun 29, 2022
@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 Jul 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: material/sidenav feature This issue represents a new feature or feature request rather than a bug or bug fix P5 The team acknowledges the request but does not plan to address it, it remains open for discussion
Projects
None yet
Development

No branches or pull requests

4 participants