Regression:[NTP]Tiles from 2 overlays appear to have been merged under single overlay
Reported by
vineetha...@etouch.net,
Oct 24
|
|||
Issue descriptionChrome Version: 70.0.3538.77 (Official Build) Revision 0f6ce0b0cd63a12cb4eccea3637b1bc9a29148d9-refs/branch-heads/3538@{#1039}(32/64-Bit) OS: Windows(7,8,8.1,10), Mac (10.13.1, 10.13.6, 10.14.1) Steps to reproduce: 1.Launch chrome and navigate to chrome://flags, click on 'Reset all to default' and relaunch browser. 2.Open NTP and press tab to get focus over gear icon and press enter, then select 'Chrome Backgrounds' option and press enter again. 3.Choose any tile under 'Select a collection' by pressing Enter. 4.In the collection overlay choose any wallpaper by clicking enter on the tile. 5.Now press Esc and observe overlay gets closed. 6.Repeat steps 1 and 2(from above) and observe that tile still appears selected. 7.Now scroll down the overlay and observe. Actual Result : 1. Tile still appears selected on reopening overlay even when it has not been applied. 2. Tiles from 2 overlays appear to have been merged under single overlay. Expected Result: 1. Tile should not appear selected after reopening overlay when the wallpaper has not been applied. 2. Two overlays should be opened one for selecting a collection and another for choosing a specific wallpaper. This is a regression issue, broken in 'M-70', and below is the bisect info: Good Build:70.0.3537.0 (Revision: 587303) Bad Build :71.0.3538.0 (Revision: 587811) Change-Log URL: https://chromium.googlesource.com/chromium/src/+log/70.0.3537.0..70.0.3538.0?pretty=fuller&n=10000 Suspecting:r587331? @sweilun: Pardon me if this is an intended change. 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. Providing suspect through 'Change-Log' because unable to perform bisect using 'per-revision' and 'chromium bisect' script. 2. Tried performing 'per revision' bisect on multiple Windows, Mac machines but unable to perform the same since getting "RuntimeError: We don't have enough builds to bisect" error . 3. Unable to perform 'chromium bisect' script as issue is not reproducible on chromium builds. 4. This is an issue with remote NTP. 5. Issue is also reproducible on latest Canary build #72.0.3590.0 Thank you
,
Oct 30
,
Nov 15
|
|||
►
Sign in to add a comment |
|||
Comment 1 by ramyan@chromium.org
, Oct 24Owner: ----
Status: Available (was: Assigned)