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

Issue 735426 link

Starred by 1 user
Status: Assigned
Owner:
amaralp@chromium.org
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Regression: Unwanted 'Cursor pin' is for Google logo of chrome://welcome after tap/touch on it

Reported by sans...@etouch.net, Jun 21 2017 
Chrome Version: 60.0.3112.40 (Official Build)6de35395b27b983b671c777caa9a273017e80d62-refs/branch-heads/3112@{#412} (32/64-bit)
OS: Windows 10

Steps:
1. Launch Chrome and navigate to chrome://welcome
2. Click on Google logo multiple time to make it spin and then tap/touch on it .
3. Observe

Actual: Unwanted 'Cursor pin' is for Google logo after tap/touch on it

Expected: 'Cursor pin' should not be seen for Google logo after tap/touch on it

This is regression issue broken in M-57, and below is bisect info.

Good Build: 57.0.2984.0
Bad Build: 57.0.2985.0

Narrow bisect:
https://chromium.googlesource.com/chromium/src/+log/10212c417a1326fd26f8aeee0f2f446d9f1e9793..ef71a0a844aed50e40cf74d5c5f1ac0b94639c18?pretty=fuller&n=100

Suspecting: r444116 ?

Please help to re-assign if your change is not the cause for this issue.

Note: This is touch device specific issue, same works fine via mouse click.
Actual_video.mp4
289 KB View Download
Expected_video.mp4
318 KB View Download

Comment 1 by mustaq@chromium.org, Jun 26 2017

Labels: Needs-Bisect
Owner: ----
Status: Untriaged (was: Assigned)
My CL is strictly Android-only, so doesn't affect this Windows-only bug.

Unfortunately, no other change in the suspect range seem related.

May I request another bisect in case we missed something?

Comment 2 by rbasuvula@chromium.org, Jun 27 2017

Cc: rbasuvula@chromium.org
Labels: -Needs-Bisect hasbisect-per-revision
Owner: amaralp@chromium.org
Status: Assigned (was: Untriaged)
Using the per-revision bisect providing the bisect results,
Good build:57.0.2984.0(Revision:443964).
Bad build:57.0.2985.0(Revision:444244).

You are probably looking for a change made after 444118 (known good), but no later than 444119 (first known bad).

CHANGE-LOG URL:
---------------
https://chromium.googlesource.com/chromium/src/+log/28b1bf2e4e780f510109ca4b1d61e72f024232aa..1107a295dcee2f4ee3f6c24f836c6adfa7b3830d

From the CL above, assigning the issue to the concern owner

@amaralp: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Review-Url: https://codereview.chromium.org/2201853002
Note :Windows 10 specific issue and Able to reproduce in latest Canary #61.0.3141.0

Comment 3 by amaralp@chromium.org, Mar 8 2018

Labels: -Pri-2 Pri-3
►

Sign in to add a comment