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

Issue 788106 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 767373
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression:Focus ring is not seen properly on devtools.

Reported by pranjali...@etouch.net, Nov 23 2017

Issue description

Chrome Version: 64.0.3276.0 (Official Build) ccea2aa0a41cbb3dcbbf5961be4820d428b93a4c-refs/heads/master@{#518818}(64-bit)

OS:Mac(10.13.2) 

Steps to reproduce:
1. Launch chrome, navigate to NTP and open devtools.
2. Click on ‘Customise and control DevTools’ icon > Settings > Devices.
3. Now click on ‘Add Custom Devices’ button and observe ‘device name’ textbox.

Actual Result:Focus ring is not seen properly on settings in devtools.
Expected Result:Focus ring is not seen properly on settings in devtools.

This is regression issue broken in ‘M-61’ and below per-revision bisect result

Using the per-revision bisect providing the bisect results,
Good Build: 61.0.3122.0
Bad Build:61.0.3123.0

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

CHANGE-LOG 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/+log/067ae0c565d431228fbcada9823b47d371f54b7d..ea62429d8dcfa87cd32a2ce9dcaa83167c827b99

Suspect :  https://chromium.googlesource.com/chromium/src/+/ea62429d8dcfa87cd32a2ce9dcaa83167c827b99


 
Actual_result.mov
1.8 MB Download
Expected_result.mov
2.0 MB Download
Labels: hasbisect-per-revision
Cc: shrike@chromium.org

Comment 3 by l...@chromium.org, Nov 27 2017

Labels: -Pri-1 Pri-2
Mergedinto: 767373
Status: Duplicate (was: Assigned)

Sign in to add a comment