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

Nested menu items for parent shown with *ngIf are visible after click only #6731

Closed
Gribanov opened this issue Aug 30, 2017 · 1 comment · Fixed by #6807
Closed

Nested menu items for parent shown with *ngIf are visible after click only #6731

Gribanov opened this issue Aug 30, 2017 · 1 comment · Fixed by #6807
Assignees

Comments

@Gribanov
Copy link

Bug, feature request, or proposal:

Bug. When menu item is shown via *ngIf and it has child menu this child menu becomes visible only after clicking on parent menu item. If parent menu item is "static" (i.e. is always in template) child menu becomes visible on hover.

What is the expected behavior?

Child menu becomes visible on hovering over parent

What is the current behavior?

Child menu becomes visible on clicking parent menu item

What are the steps to reproduce?

See
http://plnkr.co/edit/xsqusDiMhDHCdHrSbMOa?p=preview
"Show menu" button has menu with two items that have child menu. One item ("Always enabled child items") is always enabled, its child menu is shown on mouseover. Another menu item ("Triggered child items") is controlled by "Toggle" button. If it's visible you need to click on it to reveal its child menu

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

    "@angular/common": "4.3.2",
    "@angular/compiler": "4.3.2",
    "@angular/core": "4.3.2",
    "@angular/flex-layout": "2.0.0-beta.8",
    "@angular/forms": "4.3.2",
    "@angular/http": "4.3.2",
    "@angular/material": "^2.0.0-beta.10"

Browsers: latest stable Chrome, Firefox, IE11

@crisbeto crisbeto self-assigned this Aug 30, 2017
@crisbeto crisbeto added the has pr label Sep 2, 2017
crisbeto added a commit to crisbeto/material2 that referenced this issue Sep 2, 2017
Fixes not being able to open a sub-menu if its trigger is added after initialization.

Fixes angular#6731.
tinayuangao pushed a commit that referenced this issue Sep 6, 2017
…#6807)

Fixes not being able to open a sub-menu if its trigger is added after initialization.

Fixes #6731.
@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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants