Skip to content

docs: add example for using ripples within table #22797

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 2 commits into from
May 26, 2021

Conversation

devversion
Copy link
Member

Fixes #11883

@devversion devversion added docs This issue is related to documentation merge safe target: patch This PR is targeted for the next patch release labels May 25, 2021
@devversion devversion requested a review from andrewseguin May 25, 2021 20:51
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 25, 2021
Copy link
Contributor

@mmalerba mmalerba left a comment

Choose a reason for hiding this comment

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

LGTM

@mmalerba mmalerba added action: merge The PR is ready for merge by the caretaker merge: fix commit message When the PR is merged, rewrites/fixups of the commit messages are needed labels May 25, 2021
@wagnermaciel wagnermaciel merged commit d7e2109 into angular:master May 26, 2021
wagnermaciel pushed a commit that referenced this pull request May 26, 2021
* docs: add example for using ripples within table

(cherry picked from commit d7e2109)
@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 Jun 26, 2021
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 docs This issue is related to documentation merge: fix commit message When the PR is merged, rewrites/fixups of the commit messages are needed target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document limitation of matRipple on native table rows and possible solutions
3 participants