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(ripple): remove webkit touch highlights from ripple containers #12082

Merged
merged 1 commit into from Jul 11, 2018

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Jul 5, 2018

Since the ripples are feedback enough that the element was touched, we should disable the native feedback on touch devices so it doesn't overlap with the ripples. These changes go through the various clickable ripple triggers and remove the Webkit highlighting.

Since the ripples are feedback enough that the element was touched, we should disable the native feedback on touch devices so it doesn't overlap with the ripples. These changes go through the various clickable ripple triggers and remove the Webkit highlighting.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Jul 5, 2018
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jul 5, 2018
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

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

In general LGTM to me. Would it be worth considering the slide-toggle etc. as well?

@crisbeto
Copy link
Member Author

crisbeto commented Jul 6, 2018

These were the components that both have a ripple and are entirely clickable so it was an easy assumption to make that they'll get the overlay (also verified by manual testing). At some point we can go through everything and see if there are any more components that need the same.

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Jul 6, 2018
@ngbot

This comment has been minimized.

@devversion
Copy link
Member

That's fine by me. Just wanted to see if we should consider doing this for the slide-toggle etc. as well. Since those also are completely clickable and also have a ripple feedback it would be reasonable.

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 merged commit 8e2ff1f into angular:master Jul 11, 2018
victoriaaa234 pushed a commit that referenced this pull request Jul 25, 2018
…12082)

Since the ripples are feedback enough that the element was touched, we should disable the native feedback on touch devices so it doesn't overlap with the ripples. These changes go through the various clickable ripple triggers and remove the Webkit highlighting.
@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 9, 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.

None yet

4 participants