Regression : Glimpse of scroll border line is seen after clicking on 'Add' button in chrome://md-settings/autofill.
Reported by
rp...@etouch.net,
Apr 11 2017
|
||||
Issue descriptionVersion: 59.0.3068.1 2f0cdddf2601f4c9862b35013630d230da469892-refs/branch-heads/3068@{#1} OS: Windows (7,8,8.1,10) What steps will reproduce the problem? 1. Launch chrome, navigate to chrome://md-settings/autofill and click on 'Add' button and immediately observe border line under Add address in overlay Actual: Glimpse of scroll border line is seen under Add address header after clicking on 'Add' button Expected: Glimpse of scroll border line should not be seen under Add address header after clicking on 'Add' button This is regression issue, broken in ‘M 59’ and will soon update other info : Good build:59.0.3067.0 Bad build: 59.0.3068.1
,
Apr 11 2017
Using the per-revision bisect providing the bisect results, Good build:59.0.3067.0 (Revision:463157). Bad build:59.0.3068.1 (Revision:463474). You are probably looking for a change made after 463372 (known good), but no later than 463373 (first known bad). CHANGE-LOG URL: --------------- https://chromium.googlesource.com/chromium/src/+log/1e0366fc5f961223c1862ff96a0bcd1302df32cd..fee40485e1568f0a7121576d722f2b66a5832c65 From the CL above, assigning the issue to the concern owner @scottchen: 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/2795763003 Note :Able to reproduce the issue in Win 10.0,Ubuntu 14.04 & Mac 10.12.3 and Able to reproduce in latest Canary #59.0.3068.1
,
Apr 12 2017
Just to clarify, that's cr_dialog's top-border showing for a split second, not a scroll bar. Will investigate.
,
Apr 14 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fb69cfff512407b7d1e412a4a0ef71d9019daa8d commit fb69cfff512407b7d1e412a4a0ef71d9019daa8d Author: scottchen <scottchen@chromium.org> Date: Fri Apr 14 00:07:09 2017 MD Settings: in cr_dialog, prevent intersectionObserver from firing early. Currently the intersectionObesrver's handler gets triggered twice as cr-dialog renders, reporting that it's intersecting with topMarker even though scrollTop is 0. Delaying adding the observer until next render loop fixes the issue. BUG= 710355 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2815623005 Cr-Commit-Position: refs/heads/master@{#464617} [modify] https://crrev.com/fb69cfff512407b7d1e412a4a0ef71d9019daa8d/chrome/test/data/webui/cr_elements/cr_dialog_test.js [modify] https://crrev.com/fb69cfff512407b7d1e412a4a0ef71d9019daa8d/ui/webui/resources/cr_elements/cr_dialog/cr_dialog.js
,
Apr 17 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by rp...@etouch.net
, Apr 11 20173.3 MB
3.3 MB Download