Issue metadata
Sign in to add a comment
|
Regression: 'More action' menu list does not disappear after clicking anywhere on page.
Reported by
jshan...@etouch.net,
May 12 2016
|
||||||||||||||||||||||||
Issue descriptionChrome Version: 52.0.2734.0 (Official Build) dc1c91063493c22633664e04ca52ea4881480068-refs/heads/master@{#393126}-32/64 bit OS:Windows(7,8,10), Mac(10.10.5)(10.11.4), Linux(ubuntu 14.04 LTS). Steps: 1. Launch chrome, go to NTP and open dev-tool window. 2. Toggle device toolbar and select capture screenshot from 'More options' menu(Downloads bar appears at the bottom of the page). 3. Click on 'SHOW ALL' (chrome://downloads page opens),navigate to chrome://downloads on NTP and resize the browser window. 4. Now click on 'More actions' menu icon and then click anywhere on the page and observe. Actual:'More action' menu list does not disappear after clicking anywhere on page. Expected:'More action' menu list should disappear after clicking anywhere on page. Good build: 52.0.2709.0 Bad build: 52.0.2711.0 This is regression issue broken in ‘M 52’ and below is narrow bisect: https://chromium.googlesource.com/chromium/src/+log/d7c335ae8182ad53a52439b5de283ef5d0970737..a794ae416acf94cb247d8ca0e8554863f5d9c1d8?pretty=fuller&n=100 Suspecting: r387633 ? Please help to reassign if your change is not the cause for this issue.
,
May 12 2016
@dbeam: I guess this means that crbug.com/604685 needs to be marked as RB-Stable too.
,
May 12 2016
Actually I am going to un-deduplicate this for now, because the repro steps are a bit different, even though the symptom seems similar.
,
May 12 2016
I am able to reproduce the bug. Simplifying the repro steps below. 1) Navigate to chrome://downloads, but make it so that it is already in device mode (see comment#1 on a way to do this). 2) Once in downloads, deactivate device mode. 3) Try to open the menu by clicking on the dots. It does not open Something seems to not be initialized correctly when the page loads in "device" mode. Given those steps, I don't think the severity of this bug is too high, perhaps we can remove RB-Stable?
,
May 12 2016
FYI, the problem is also reproducible on the paper-menu-button demo page at https://elements.polymer-project.org/elements/paper-menu-button?view=demo:demo/index.html&active=paper-menu-button. 1) Navigate to demo page, turn on device mode and reload the page. 2) Exit device mode. 3) Try to open any of the menus, nothing happens.
,
May 12 2016
Per discussion with @dbeam, I am removing RB-Stable. The problem occurs only when a page is loaded in device mode, and then transitioned to normal mode. Needs further investigation to pin-point which Polymer component is the culprit.
,
May 12 2016
,
May 12 2016
FYI, filed https://github.com/PolymerElements/paper-menu-button/issues/81 about this.
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 6 2016
,
Jul 10 2016
This issue is Pri-1 but has already been moved once. Lowering the priority and moving to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 29 2016
,
Oct 3 2016
Note: Above issue is not reproducible on latest canary version: 55.0.2878.0, hence marking it as wontfix |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ashej...@chromium.org
, May 12 2016