New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 665214 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner: ----
Closed: May 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome
Pri: 2
Type: Bug



Sign in to add a comment

An InkDropRipple is visible on extension buttons when clicked inside the chrome menu

Project Member Reported by bruthig@chromium.org, Nov 15 2016

Issue description

Actual:

The ripple effect of the ink drop is visible when an extension button in the Chrome menu is clicked on.

Expected:

Only the highlight effect of the ink drop should visible.
 
ripple on extension buttons in menu.png
388 KB View Download
Hmm.  The omnibox star and the Chrome menu button itself are both similarly-sized objects with a similar highlight, a dropdown/menu that appears on click, and a ripple effect.  But in those cases the ripple is slower, making things look less glitchy.  Can we just make the ripple here look good and be consistent with our other ripples, instead of removing it?

It seems like we're busy trying to add ripples for most of the remaining top-chrome UI elements that don't have them, so I'm a bit mystified why we want to remove some here, instead of just making sure they look nice.  What's the logic?
Cc: varkha@chromium.org
The highlight is supposed to remain (i.e. the rounded rectangle), the ripple (i.e. the circle) was never supposed to be there.  Adding varkha@ for reasoning as he added it in the first place.
I understood that your position was that the ripple was not supposed to be there, but I'm contesting it.  I think from a consistency and UI feedback perspective, this should have a ripple, it's just that it should have one that looks good, as e.g. the Star ripple does; and it currently doesn't.

I'd like to understand _why_ you feel the ripple is "not supposed to be there", from a design perspective.
Because no other UI elements inside a normal menu have a ripple.  The highlight is only used because it resembles the hot tracking effect used by the text rows.  So it's a question of what other elements should we be consistent with.
Cc: msrchandra@chromium.org pkasting@chromium.org rbasuvula@chromium.org nyerramilli@chromium.org
 Issue 664910  has been merged into this issue.
Cc: ranjitkan@chromium.org
 Issue 706283  has been merged into this issue.
Status: Started (was: Available)
CL: https://codereview.chromium.org/2914043002/
Project Member

Comment 9 by bugdroid1@chromium.org, May 31 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/63422e6364f834a36ac69cc1a743ad4bcabc4c09

commit 63422e6364f834a36ac69cc1a743ad4bcabc4c09
Author: bruthig <bruthig@chromium.org>
Date: Wed May 31 23:47:47 2017

Changed extension buttons to use a flood-fill ripple when in the chrome menu.

BUG= 665214 
TEST=none

Review-Url: https://codereview.chromium.org/2914043002
Cr-Commit-Position: refs/heads/master@{#476094}

[modify] https://crrev.com/63422e6364f834a36ac69cc1a743ad4bcabc4c09/chrome/browser/ui/views/toolbar/toolbar_action_view.cc
[modify] https://crrev.com/63422e6364f834a36ac69cc1a743ad4bcabc4c09/chrome/browser/ui/views/toolbar/toolbar_action_view.h

Status: Fixed (was: Started)

Sign in to add a comment