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

fix(menu): not picking up indirect descendant items #9971

Merged
merged 1 commit into from
Feb 18, 2018

Conversation

crisbeto
Copy link
Member

Fixes the menu directive not picking up menu items that aren't direct descendants of the panel.

Fixes #9969.

Fixes the menu directive not picking up menu items that aren't direct descendants of the panel.

Fixes angular#9969.
@crisbeto crisbeto requested a review from kara as a code owner February 15, 2018 20:28
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Feb 15, 2018
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Feb 17, 2018
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Feb 17, 2018
@jelbourn jelbourn merged commit 5ca154b into angular:master Feb 18, 2018
tinayuangao pushed a commit that referenced this pull request Feb 20, 2018
Fixes the menu directive not picking up menu items that aren't direct descendants of the panel.

Fixes #9969.
andrewseguin pushed a commit that referenced this pull request Feb 20, 2018
Fixes the menu directive not picking up menu items that aren't direct descendants of the panel.

Fixes #9969.
crisbeto added a commit to crisbeto/material2 that referenced this pull request Feb 22, 2018
Reverts the changes from angular#9971, because they break the case where a mat-menu is placed inside another mat-menu, causing the keyboard controls to be thrown off and nested menus not to work. Having a solution that supports both cases will require moving some more code around.

Fixes angular#10083.
crisbeto added a commit to crisbeto/material2 that referenced this pull request Feb 22, 2018
Reverts the changes from angular#9971, because they break the case where a mat-menu is placed inside another mat-menu, causing the keyboard controls to be thrown off and nested menus not to work. Having a solution that supports both cases will require moving some more code around.

Fixes angular#10081.
@crisbeto crisbeto mentioned this pull request Feb 22, 2018
josephperrott pushed a commit that referenced this pull request Feb 22, 2018
mmalerba pushed a commit to mmalerba/components that referenced this pull request Feb 26, 2018
jelbourn pushed a commit to jelbourn/components that referenced this pull request Feb 27, 2018
@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 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[bug mat-menu]: nested menu not closing when mat-menu-item is not directly inside mat-menu
3 participants