Issue metadata
Sign in to add a comment
|
Regression: Context menu seems misplaced after opening it via using touch.
Reported by
db...@etouch.net,
Jan 22 2018
|
||||||||||||||||||||||||
Issue descriptionChrome Version: 66.0.3328.0 (Official Build) Revision 1629a284e7c7c2ea5e562d9f242a84992cab5ed7-refs/heads/master@{#530801} OS: Windows(10 Touch device) What steps will reproduce the problem? (1) Launch chrome, open NTP and tap/touch in omnibox (2) Observe context menu Actual: Context menu seems misplaced after opening it via using touch. Expected: Context menu should not misplaced after opening it via using touch. This is a touch specific regression issue, broken in 'M64', below is bisect info: Good Build: 64.0.3256.0 Bad Build: 64.0.3257.0 You are probably looking for a change made after 513360 (known good), but no later than 513361 (first known bad). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+lo/a28eb737c4c9424d7656ada19b688af854777968..1eca7aba022c190ea02e34dbd4ae52a8f5f88bbc Suspect:https://chromium.googlesource.com/chromium/src/+/1eca7aba022c190ea02e34dbd4ae52a8f5f88bbc Note: Issue is not seen on Windows(7,8), Liunx(14.04 LTS) and Mac(10.12.6,10.13.1,10.13.3) and also using click.
,
Jan 22 2018
,
Jan 23 2018
This is the same as Issue 791507 But it shouldn't happen in m64 unless chrome://flags/#secondary-ui-md is enabled, which it is not by default - can you check?
,
Feb 2 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by db...@etouch.net
, Jan 22 2018