Issue metadata
Sign in to add a comment
|
Regression:Unable to click in search box after navigating to chrome://flags while print preview is open.
Reported by
shruti.j...@etouch.net,
Sep 17
|
||||||||||||||||||||||||
Issue description
Chrome Version : 71.0.3554.0 (Official Build) Revision50b24262ba0c4e14c723112f9aad3686dc6462c1-refs/branch-heads/3554@{#1}(64-bit)
OS: Win(7,8,8.1,10) and Linux(14.04 LTS)
Steps to reproduce:
1.Launch chrome and open NTP give print command (ctrl+p).
2.In the same NTP navigate to chrome://flags while print preview is open.
3.Observe search box field on chrome://flags.
Actual Result:Unable to click in search box after navigating to chrome://flags while print preview is open.
Expected Result: After step 2, search-box should work as expected on chrome://flags.
This is a regression issue, broken in 'M-70' and below is the bisect info:
Good build: 70.0.3536.0(Revision: 587137)
Bad build : 70.0.3537.0(Revision: 587302)
You are probably looking for a change made after 587266 (known good), but no later than 587277 (first known bad).
CHANGE-LOG URL:
https://chromium.googlesource.com/chromium/src/+log/578be39046de0eb8ad2c103b3a98dda76b5651b2..d6a9618ea9be2c4a999ad0b36bd2989eedebdb25
Suspect: https://chromium.googlesource.com/chromium/src/+/738ea19831a4395bff3066a8ce994482ac8b44d6
@Avi Drissman : 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. Tried to perform 'per-revision' bisect but it shows "We don't have enough builds to bisect" error message (tried on different machines but still got the same error.)
2. Hence providing suspect through 'Chromium bisect'.
3.Issue is not seen on Mac(10.12.6, 10.13.1, 10.14, 10.13.6)
Kindly refer the attached screen-cast.
Thank You.
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by a...@chromium.org
, Sep 24Status: Duplicate (was: Assigned)