Bug in chrome hover when window.open() called.
Reported by
aquapu...@gmail.com,
Apr 7 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce the problem: 1. Select square to open container 2. select menu item 3. close open window. 4. select square again ** BUG encountered- as you can see the menu item is highlighted as if it were hovered ** What is the expected behavior? hover should be normal upon reselecting drop down What went wrong? Hover is staying on Did this work before? N/A Does this work in other browsers? Yes Chrome version: 57.0.2987.133 Channel: stable OS Version: OS X 10.9.5 Flash Version: Super annoying although minor makes makes menus looks very unprofessional...
,
Apr 7 2017
Were you running on Mac OS? It seems this is an issue for others too see: http://stackoverflow.com/questions/43278738/bug-in-chrome-hover-when-window-open-called What's a bisect?
,
Apr 10 2017
,
Apr 25 2017
Able to reproduce this issue on Mac 10.12.4 with chrome version #58.0.3029.81 and but not on Dev #59.0.3071.15, Canary #60.0.3079.0 Issue fixed in M59 Bisect Info: =========== Good build : 59.0.3062.0, Revision Range -461587 Bad build : 59.0.3061.0, Revision Range -461353 After executing the bisect(old) script in “reverse”, i got the following CL's between good and bad build versions =========================================== https://chromium.googlesource.com/chromium/src/+log/d60206ee7cd61fecbceceb5e8e8b9a73de4b00c3..3f2db89d6d660abe00760144e734ccb9963cce2a The suspecting Change Log is : ----------- https://chromium.googlesource.com/chromium/src/+/3f2db89d6d660abe00760144e734ccb9963cce2a Review-Url: https://codereview.chromium.org/2778153003 ecobos@- Could you please look into this issue, if it's related to your change please merge into M-58 Note: ------ Not able reproduce this issue on Window 10 and Ubuntu 14.04 on stable #58.0.3029.81
,
Apr 25 2017
****Correction**** For above bisect "per-revision" bisect script was used.
,
Apr 25 2017
Yes, it's definitely related. Can you point me to a guide to upstream it to M-58? Never had to do it so far.
,
Apr 25 2017
,
Apr 26 2017
#7: The process is: 1. Create and land a fix that's as minimal and safe as possible. 2. Add the Merge-Request-58 label. 3. Wait for approval. 4. Use git-drover to cherry pick the fix into the branch (you'll be told which): https://www.chromium.org/developers/how-tos/drover
,
Aug 31 2017
,
Oct 18 2017
Hi ecobos@, Has there been any progress here?
,
Oct 18 2017
Yeah, this was never upstreamed, because it felt risky enough to not be done. It should be fixed on trunk though, and probably shipped a while ago already.
,
Nov 29 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by a...@chromium.org
, Apr 7 2017