-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Freature Request: callback when backdrop is clicked for md-sidenav #1427
Comments
I'll implement the simpler informational callback for now (as a simple event emitter on the |
This allows clients to distinguish between close events caused by calling close() and those caused by the backdrop being clicked. Closes angular#1427
This allows clients to distinguish between close events caused by calling close() and those caused by the backdrop being clicked. Closes angular#1427
This allows clients to distinguish between close events caused by calling close() and those caused by the backdrop being clicked. Closes angular#1427
* feat(sidenav): emit event when backdrop is clicked This allows clients to distinguish between close events caused by calling close() and those caused by the backdrop being clicked. Closes #1427 * Address review comments
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug, feature request, or proposal:
Feature Request.
What is the expected behavior?
I would like to be called back when the overlay for
md-sidenav
is clicked.What is the current behavior?
There is no callback available.
What are the steps to reproduce?
N/A
What is the use-case or motivation for changing an existing behavior?
I have a layout where I display a sub-pane using a sidenav. This is displayed in a router outlet within the sidenav component. Clicking a button on the main page changes the route and opens the sidenav to display an edit screen/popup. I want to be called back when the user clicks on the sidenav overlay, so that I can change the route back to the main page's route. Using the
onCloseStart
andonClose
events on the sidenav itself is not really right for this.Which versions of Angular, Material, OS, browsers are affected?
N/A
Is there anything else we should know?
I would be more than happy to put up a pull-request for this. I would like to ask the community whether they would want control via the callback whether the sidenav should close or not, or whether just an informational callback (e.g. event) to inform that sidenav will be closing is enough (the latter is fine for my use-case).
The text was updated successfully, but these errors were encountered: