Skip to content

fix(material/menu): getLabel not working if text is inside indirect descendant node #20705

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

Merged
merged 1 commit into from
Oct 16, 2020

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Oct 2, 2020

Currently MatMenuItem.getLabel only looks at direct descendant text nodes in order to figure out its text while excluding things like icons. This breaks down if there's some kind of wrapper in the menu item.

These changes fix the issue by using textContent and excluding icons specifically.

Fixes #20200.

@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release labels Oct 2, 2020
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 2, 2020
@crisbeto crisbeto force-pushed the 20200/menu-get-label branch from eb7eb8a to 67c123d Compare October 2, 2020 11:20
…escendant node

Currently `MatMenuItem.getLabel` only looks at direct descendant text nodes in order
to figure out its text while excluding things like icons. This breaks down if there's
some kind of wrapper in the menu item.

These changes fix the issue by using `textContent` and excluding icons specifically.

Fixes angular#20200.
@crisbeto crisbeto force-pushed the 20200/menu-get-label branch from 67c123d to 15cb366 Compare October 2, 2020 12:13
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 the action: merge The PR is ready for merge by the caretaker label Oct 7, 2020
@annieyw annieyw merged commit a461929 into angular:master Oct 16, 2020
annieyw pushed a commit that referenced this pull request Oct 16, 2020
…escendant node (#20705)

Currently `MatMenuItem.getLabel` only looks at direct descendant text nodes in order
to figure out its text while excluding things like icons. This breaks down if there's
some kind of wrapper in the menu item.

These changes fix the issue by using `textContent` and excluding icons specifically.

Fixes #20200.

(cherry picked from commit a461929)
@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 Nov 16, 2020
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 P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent 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(MatMenuItem): If a <span> or any other node is used in the Item label, getLabel() doesn't work
4 participants