New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 845832 link

Starred by 5 users
Status: Assigned
Owner:
bsep@chromium.org
Cc:
█ abdulsyed@chromium.org
bsep@chromium.org
nyerramilli@chromium.org
pbomm...@chromium.org
rbasuvula@chromium.org
ligim...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug-Regression
Team-Accessibility



Sign in to add a comment

Regression: [Win] Browser's minimize/maximize/close are not responding via tap-touch.

Reported by aiman.an...@etouch.net, May 23 2018 
Chrome version: 68.0.3438.0 (Official Build) Revision 92f33534f404595554fb708537b29568da70f384-refs/branch-heads/3438@{#1} (64-bit) 

OS: Win (10 Touch-Screen)

Steps to reproduce:
1. Launch chrome, and try tap-touch on Minimize/Maximize/Close button in Tab strip.
2. Observe.

Actual Result: Buttons are not responding via tap-touch. 
Expected Result: Buttons should perform necessary functions when tap-touched. 

This is a regression issue, broken in 'M-68', and will soon update other info.
Good Build:68.0.3437.0 (Revision:560454)
Bad Build: 68.0.3438.0 (Revision:560883)
Actual Result.mp4
460 KB View Download
Expected Result.mp4
1.6 MB View Download

Comment 1 by aiman.an...@etouch.net, May 23 2018

Labels: Proj-Windows10 RegressedIn-68 FoundIn-68 Target-68
Owner: bsep@chromium.org
Status: Assigned (was: Unconfirmed)
Update:

This is a regression issue, broken in 'M-68', and below is the bisect info: 

(Unable to provide bisect via new bisect script as it is giving "Not enough builds error", hence provided bisect using Chromium builds)

Good Build:68.0.3437.0 (Revision:560454)
Bad Build: 68.0.3438.0 (Revision:560883)

Narrow Bisect: 
https://chromium.googlesource.com/chromium/src/+log/7437045138faa8fb24b881a4a125555e775f8b2c..ff828877e7dd93fb123bc4d6539d93a2187334dd

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

bsep@: Could you please help to reassign if your change is not the cause for this change.

Note:
1.Issue is Win (10 Touch) specific and is not reproducible on Mac(10.12.6, 10.13.1, 10.13.5) , Linux(14.04 LTS) OS

Comment 2 by nyerramilli@chromium.org, May 23 2018

Cc: pbomm...@chromium.org gov...@chromium.org ligim...@chromium.org
Labels: ReleaseBlock-Beta
as this is Win touch specific marking as RBB, please change if required.

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

Labels: Needs-Feedback
Well, it doesn't reproduce for me on the Surfacebook in 68.0.3427.2, so either it regressed later and it's not my patch, or it's a weird hardware-specific issue like bug 831070. What computer are you using?

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

Nope, my Canary just updated to 68.0.3438.0 and they still work fine. I'm guessing this is hardware-specific again.

I'm curious: do you get a different result if you un-maximize the window?

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

Cc: -gov...@chromium.org abdulsyed@chromium.org

Comment 6 by aiman.an...@etouch.net, May 24 2018

Labels: -Needs-Feedback
Hi bsep,

w.r.t. your comment #4 I retested the Canary build #68.0.3438.0 using your scenario.

I am unable to un-maximize  the browser using tap-touch and I tested the bug on Dell Inspiron 15R.

Attaching screen-cast, kindly review.

Thank You!.
Behaviour on 68.0.3438.0 (Win-10 Touch device).mp4
1.1 MB View Download

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

Labels: -ReleaseBlock-Beta
I meant if you un-maximize using the mouse first. But yeah, that hardware has some unique issues. Not RBS; hopefully this will be fixed when I get more into general touch later.

Comment 8 by bsep@chromium.org, Jun 21 2018

Cc: bsep@chromium.org
 Issue 854592  has been merged into this issue.

Comment 9 by bsep@chromium.org, Jul 20

Labels: -Pri-1 Pri-3
►

Sign in to add a comment