Issue metadata
Sign in to add a comment
|
Regression:Glimpse of spinner is seen on reloading the chrome://settings/siteData page.
Reported by
shruti.j...@etouch.net,
Oct 18
|
||||||||||||||||||||||
Issue descriptionChrome Version: 72.0.3584.0 Revision 945ab041ec6ac3fb389f94dcbfebb1839a12a69b-refs/branch-heads/3584@{#1}(32/64 bit) OS: MAC(10.13.1,10.13.6,10.14.1) Windows(7,8,8.1,10 and Linux()14.04 LTS) OS What steps will reproduce the problem? (1) Launch chrome and navigate to chrome://settings/siteData page. (2) Reload the page and observe. Actual: Glimpse of spinner is seen on reloading the page. Expected: Glimpse of spinner should not be seen on reloading the page. This is a regression issue, broken in 'M72', and below is bisect info: Good Build:72.0.3583.0 Bad Build:72.0.3584.0 Chromium bisect info: You are probably looking for a change made after 600223 (known good), but no later than 600228 (first known bad). CHANGE-LOG URL: https://chromium.googlesource.com/chromium/src/+log/62f2f8f209a82db0dd5a311eb4f844bddb75c98e..631a939b2b9a02a05cd1db367c7ea7fb17d14f50 Suspecting: https://chromium.googlesource.com/chromium/src/+/177774d57a744b75630cba5507c3bf1ed419aea3 @dpapad: 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. Note: 1.Tried per revision bisect on Windows ,Mac and Linux OS but unable to perform the same since getting "RuntimeError: We don't have enough builds to bisect" error 2.Hence provided suspect through 'Chromium bisect' Thank You
,
Oct 18
,
Oct 30
This seems related to a couple of things: (1) The cookies are getting returned faster, which means the spinner shows up earlier. This doesn't necessarily seem like a bug. (2) The page in general is loading slower in Polymer 2 vs Polymer 1, which seems like a bug. It appears the extra delay is related to the flush() call here: https://cs.chromium.org/chromium/src/chrome/browser/resources/settings/settings_main/settings_main.js?l=193 In Polymer 1, this call takes almost no time, while in Polymer 2 it seems to trigger a bunch of updates to the iron-list. The list appears to be fully populated in both P1 and P2 at the time the flush() call is made, so it is not a difference in the length of the list. See screenshots attached of the flush() calls - this seems to work somewhat differently in Polymer 1 vs Polymer 2.
,
Nov 1
,
Nov 1
,
Nov 1
,
Dec 13
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dpa...@chromium.org
, Oct 18Cc: rbpotter@chromium.org