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

Issue 618968 link

Starred by 5 users
Status: Fixed
Owner:
█ tsergeant@chromium.org
Not on Chrome
Closed: Aug 2016
Cc:
calamity@chromium.org
█ tjsavage@chromium.org
nyerramilli@chromium.org
dbeam@chromium.org
█ tkonch...@chromium.org
█ tsergeant@chromium.org
█ msrchandra@chromium.org
dpa...@chromium.org
michae...@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

'More options' overlay of chrome://history does not get open, on performing touch and click action.

Reported by rk...@etouch.net, Jun 10 2016 
Chrome Version: 53.0.2764.0 Revision bd10cc1ecbbcc95f143d19911a6d3b81b8043d65-refs/heads/master@{#399036}(32/64 bit)
OS:Windows 10(Touch Device)

Pr-condition: 1. Enable Material Design history from chrome://flags.
               2. Create some history by navigating any webpage.

What steps will reproduce the problem?
(1) Launch chrome, navigate to chrome://history.
(2) Tap/touch on iron icon of any link(More options overlay gets opened), then click on other link's iron icon and observe. 

'More options' overlay does not get open after clicking on iron icon.

'More options' overlay should be open after clicking on iron icon.

This is a touch specific non-regression issue, seen from 'M-50'(50.0.2638.0)
Actual_Touch.mp4
606 KB View Download

Comment 1 by msrchandra@chromium.org, Jun 10 2016

Status: Untriaged (was: Unconfirmed)
Changing the status to Untriaged so that the issue could get addressed.
Thank You.

Comment 2 by scottmg@chromium.org, Jun 10 2016

Cc: dbeam@chromium.org
Labels: Proj-MaterialDesign-WebUI

Comment 3 by dbeam@chromium.org, Jun 14 2016

Cc: michae...@chromium.org dpa...@chromium.org
Owner: tjsavage@chromium.org
Status: ExternalDependency (was: Untriaged)
looks like this might be a dupe of:
https://github.com/PolymerElements/paper-dropdown-menu/issues/166

Comment 4 by tsergeant@chromium.org, Jun 22 2016

Cc: tjsavage@chromium.org
Owner: tsergeant@chromium.org
Status: Assigned (was: ExternalDependency)
We don't actually use paper-dropdown-menu so I'm going to assign this to myself to take a closer look
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 6 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by tsergeant@chromium.org, Jul 19 2016

Status: WontFix (was: Assigned)
Looks like this is an issue in Polymer itself (I can reproduce it with plain <button>s that have tap listeners).

I've filed a Polymer bug (https://github.com/Polymer/polymer/issues/3784)
and am closing this one.

Comment 7 by dbeam@chromium.org, Jul 19 2016 

tsergeant@: should this be Status: ExternalDependency instead?

how are you tracking whether the fix gets to Chrome or do you just think fixing this isn't a big deal?

Comment 8 by tsergeant@chromium.org, Jul 20 2016

Labels: -Pri-2 Pri-3
Status: ExternalDependency (was: WontFix)
Sure, I can keep an eye on the Polymer issue and close this if/when a fix rolls through.

Comment 9 by tsergeant@chromium.org, Jul 22 2016

Cc: tsergeant@chromium.org msrchandra@chromium.org ranjitkan@chromium.org
 Issue 630201  has been merged into this issue.

Comment 10 by tsergeant@chromium.org, Aug 9 2016 

Fixed by rolling Polymer to 1.6.1 in R409598
►

Sign in to add a comment