New issue
Advanced search Search tips

Issue 846103 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 832291
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Single touch-tap on window decorations (e.g. maximize button, close button) is processed twice

Project Member Reported by w...@chromium.org, May 23 2018

Issue description

Chrome Version: 67.0.3396.56
OS: Win10, Lenovo Yoga 700(?)

What steps will reproduce the problem?
(1) Launch Chrome.
(2) Create two Chrome windows, both maximized.
(3) Tap the close button on the top-most window.

What is the expected result?

Expect that the top-most window closes, to reveal the one underneath.

What happens instead?

Both windows are closed, as though the tap is processed twice (e.g. as though we're processing both the press and the release events).

The same issue can be reproduced with the maximize button: maximize a Chrome window and then tap on the maximize button, and it will restore and then immediately re-maximize (though this may depend on the position it restores to also being under the tap position). 
 
Cc: bsep@chromium.org
Likely cause is Bret's fixes..

https://chromium.googlesource.com/chromium/src.git/+/fdafd691ac38754d9b2e2ef1990d0b478985ac0b

bsep@ can you own this one?
Labels: -Type-Bug -Pri-3 Pri-1 Type-Bug-Regression
Labels: ReleaseBlock-Dev

Comment 4 by bsep@chromium.org, May 23 2018

Labels: -ReleaseBlock-Dev
That's annoying... that's exactly the bug I was trying to fix (see  bug 832291 ). It's definitely fixed on the Surfacebook, so there's something hardware-dependent going on.

Removing ReleaseBlock because I think this is pre-existing, I just changed which hardware it affects. If someone can get me a Yoga I'll look at it...

Comment 5 by bsep@chromium.org, May 23 2018

Cc: -bsep@chromium.org
Owner: bsep@chromium.org
Status: Assigned (was: Untriaged)
I'll make a larger effort to fix touch on Windows when I have more time, so I'm fine taking ownership of this.

Comment 6 by w...@chromium.org, May 24 2018

Re #5: Sorry, I may have got the Chrome version wrong (thought it is a Dev /M68 install, but I realised it may be Beta/M67) - I'll check tonight and update.

Comment 7 by w...@chromium.org, May 24 2018

Description: Show this description

Comment 8 by w...@chromium.org, May 24 2018

Labels: -M-68 M-67
Confirmed that this device is running M67, not M68.

Comment 9 by bsep@chromium.org, May 24 2018

Mergedinto: 832291
Status: Duplicate (was: Assigned)
Okay, then it's probably the same bug. Re-open if it's not fixed in 68.

Sign in to add a comment