New issue
Advanced search Search tips

Issue 804218 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 791507
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



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 description

Chrome 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.
 
Actual_Touch.mp4
682 KB View Download
Expected_touch.mp4
1.3 MB View Download

Comment 1 by db...@etouch.net, Jan 22 2018

Labels: RegressedIn-64 Target-65 FoundIn-66 Target-66 FoundIn-64 FoundIn-65 Target-64
Note: Issue is also seen on M64 Beta(#64.0.3282.99) and M65 Dev(#65.0.3322.3)

Comment 2 by db...@etouch.net, Jan 22 2018

Labels: Proj-Windows10 OS-Windows

Comment 3 by tapted@chromium.org, Jan 23 2018

Cc: kylixrd@chromium.org
Mergedinto: 791507
Status: Duplicate (was: Assigned)
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?
Labels: ET-MUM-Reported

Sign in to add a comment