Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not just
opacity: 0as for the other selectors? Also looks like on touch devices the persistent ripple can be hidden without the:hoverright?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted to prevent any selectors with a higher specificity from reintroducing the
opacity.I'm not sure I get it. Do you mean using the focus monitor classes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, just feels a bit odd to use
display: nonebecause I personally just usedisplay: noneif something needs to be hidden for a longer time-span. But in this case, it can quickly toggle thedisplaybecause you're only hiding the persistent ripple if the:hoverpseudo element is activated.I've meant that we could just set
display: nonepermanently if@media (hover: none)is activated because in no other scenario on touch, the persistent ripple shows up (after #13562)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's what I did initially (always having
display: none), but I decided to keep the more specific selector in case the input receives keyboard focus somehow (e.g. programmatically through theFocusMonitoror by pressing the "Next" button on the virtual keyboard).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually thinking about it more, as it is now it allows us to keep the focus indication for hybrid devices that have both a touchscreen and a keyboard.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair enough. Can you add this into a comment? doesn't have to be too detailed.