New issue
Advanced search Search tips

Issue 898072 link

Starred by 3 users
Status: Assigned
Owner:
paulir...@chromium.org
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Focus Ring is seen chopped from top in first entry of 'Opportunities' section in DevTools .

Reported by shruti.j...@etouch.net, Oct 23 
Chrome Version : 71.0.3578.20 (Official Build) be2b6ea800808b865cd07ab76acf9e2a009c045a-refs/branch-heads/3578@{#254} 32/64 bit
OS : Mac(10.13.1, 10.13.6, 10.14.1), Linux(14.04), Windows(7,8,10)

Test URL: https://you.dj/

What steps will reproduce the problem?
1. Launch chrome, navigate to above URL.
2. Click on three dots and under 'More Tools' select 'Developer Tools'
3. Perform 'Audit' on page  and Press Tab focus .
4. Observe Focus ring under 'Opportunities' section.

Actual Result : Focus Ring is seen chopped from top in first entry of 'Opportunities' section.
Expected Result : Focus Ring should be seen properly in first entry of 'Opportunities' section.

This is a regression issue broken in M-71 and will soon inform the bisect information:
Good Build : 71.0.3577.0 
Bad Build  : 71.0.3578.0 

Kindly refer the attached screencast from drive link:
https://drive.google.com/open?id=1kRd9jQ1q6z11jTnqYBoKKZi4ke2lR2BE

Thank you..!

Comment 1 by shruti.j...@etouch.net, Oct 23

Labels: hasbisect
Owner: paulir...@chromium.org
Status: Assigned (was: Unconfirmed)
Update:

Bisect info:

You are probably looking for a change made after 598588 (known good), but no later than 598625 (first known bad).
CHANGELOG URL:

https://chromium.googlesource.com/chromium/src/+log/ed7a7b47cb438384c71faa43c00f3fc0e2f62fc5..16dcfadaa3443e1ad0cd6d91be2cd8abe8b0623f

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

@Paul Irish :Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.


Note:

1.Unable to provide 'per-revision' bisect as it shows "We don't have enough builds to bisect" error message.
2.Tried on other machines but still getting the same error again.
3.Hence provided suspect through 'Chromium bisect'.
4.Issue is also seen on latest canary #72.0.3589.0.

Thank you..!
►

Sign in to add a comment