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

Menu bar component #14924

Open
Angelinsky7 opened this issue Jan 23, 2019 · 3 comments
Open

Menu bar component #14924

Angelinsky7 opened this issue Jan 23, 2019 · 3 comments
Labels
area: material/menu feature This issue represents a new feature or feature request rather than a bug or bug fix P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects

Comments

@Angelinsky7
Copy link

What is the expected behavior?

When creating a menu inside a toolbar when clicking on the first item (a button that open a menu) i would except the second menu to open when the mouse enter the next menu item in the toolbar.

What is the current behavior?

You need to click on the second item of the menu to open the second menu. This is totally logical, because root menu items are simple button, but if you try to create a complex menu toolbar, users are used to menu that open automatically without the need to click (apart from the first time)

What are the steps to reproduce?

you can look here for the kind of menu that i mean : https://stackblitz.com/edit/dynamic-nested-topnav-menu?file=app%2Fapp.component.html
if you click on the first item ('DevFestFL') and them move your mouse on "Didney" or "Orlando" you would except, as a user, that the corresponding menu open automatically. Instead, you need to click on the item.

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

"@angular/animations": "~7.2.0",
"@angular/cdk": "~7.2.1",
"@angular/common": "~7.2.0",
"@angular/compiler": "~7.2.0",
"@angular/core": "~7.2.0",
"@angular/forms": "~7.2.0",
"@angular/material": "^7.2.1",
"@angular/platform-browser": "~7.2.0",
"@angular/platform-browser-dynamic": "~7.2.0",
"@angular/router": "~7.2.0",
"core-js": "^2.5.4",
"hammerjs": "^2.0.8",
"rxjs": "~6.3.3",
"tslib": "^1.9.0",
"zone.js": "~0.8.26"

Is there anything else we should know?

I understand why this is happening and it seems that we would need to have something like a mat-menu-toolbar that could automatically 'open' a mat-menu-item and show it to the user (horizontally or vertically) like that we could have a coherent way of showing simple menu and complex one without so much effort.

thanks !

@mmalerba mmalerba added the needs triage This issue needs to be triaged by the team label May 20, 2020
@crisbeto
Copy link
Member

This sounds similar to the menu bar component we had in Angular.js Material.

@crisbeto crisbeto changed the title [Menu] Cannot pass from one menu to another Menu bar component May 25, 2020
@crisbeto crisbeto added feature This issue represents a new feature or feature request rather than a bug or bug fix P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent and removed needs triage This issue needs to be triaged by the team labels May 25, 2020
@crisbeto crisbeto removed their assignment May 25, 2020
@crisbeto crisbeto added this to Triaged in triage #1 via automation May 25, 2020
@angular-robot
Copy link
Contributor

angular-robot bot commented Feb 2, 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/menu feature This issue represents a new feature or feature request rather than a bug or bug fix P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
No open projects
triage #1
  
Triaged
Development

No branches or pull requests

4 participants