Issue metadata
Sign in to add a comment
|
Regression: Unwanted glimpse of error message focus ring is seen for https://www.facebook.com/
Reported by
khushal....@etouch.net,
Oct 5
|
||||||||||||||||||||||
Issue descriptionChrome Version: 71.0.3571.0 (Official Build) Revision b588fc0229844f0b6758d5ec481c152c891b6d9b-refs/branch-heads/3571@{#1} (64-bit) OS: Mac (10.12.6, 10.13.1, 10.13.6, 10.14.1) Test URL: https://www.facebook.com/ What steps will reproduce the problem? 1. Launch chrome and navigate to above URL. 2. Click on 'Reload this page' button for 2-3 times. 3. Now Observe the 'First Name' textfield of the page. Actual Result: Unwanted glimpse of error message focus ring is seen on 'First Name' textfield on reloading the page. Expected Result: Glimpse of error message focus ring should not be seen on 'First Name' textfield on reloading the page. This is a Regression issue seen from 'M-70' and below is the manual bisect range:- Good Build: 70.0.3504.0 (Revision: 578511) Bad Build: 70.0.3505.0 (Revision: 578873) Using Per-revision bisect script, providing the bisect info below:- You are probably looking for a change made after 578641 (known good), but no later than 578642 (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/4915abd31c41536b527d54d1aa6ac0fe7134540c..312cc70dbd68686332c4a489bafba694181e0339 Suspecting: https://chromium.googlesource.com/chromium/src/+/312cc70dbd68686332c4a489bafba694181e0339 @sdy: 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. Issue is also seen on M-70 Beta (version #70.0.3538.45) & M-71 Dev (version #71.0.3569.0). 2. Issue is not seen on Win (7, 8, 8.1, 10) & Linux (14.04 LTS). Please refer the attached screen-cast. Thank You..!!
,
Oct 8
Update: With respect to comment #1, @rtoy: This issue is not reproducible now on chrome build #70.0.3538.45 and #71.0.3573.0. None of the extension was installed earlier and issue was reproducible without extension. Thank You..!!
,
Oct 8
If it's not reproducible in Chrome 71, then I think we can consider this fixed.
,
Oct 9
Marking this fixed based on earlier comments. Please reopen if this is still happening in 71 and beyond. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by rtoy@chromium.org
, Oct 6