New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 609762 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Chrome://history page does not load properly after opening it from 'Open tabs' option.

Reported by rk...@etouch.net, May 6 2016

Issue description

Chrome Version: 52.0.2726.0 (Official Build)58a611fea9de21de789f594b0e95c5147d74b519-refs/heads/master@{#391959} 32/64-bit.
OS: Windows(7,8,10), Mac(10.10.5, 10.11.4), Linux(Ubuntu 14.04 LTS).

Pre-condition: 1. Enable ‘Material Design History’ flag.
               2. Sig into chrome with valid credentials.

What steps will reproduce the problem?
(1) Launch chrome, navigate to chrome://history 2 3 times.
(2) Sign out from the chrome,then again sign into chrome with same account and navigate to chrome://history
(3) Go to 'Open tabs' and right click on 'History' link, select 'Open link in new tab' and observe. 

Chrome://history page does not get load properly after opening it from open tabs option.

Chrome://history page should be load properly after opening it from open tabs option.

This is a regression issue, broken in 'M-52', below is bisect info:

Good build: 52.0.2724.0
Bad Build: 52.0.2725.0

CahngeLog URL:
https://chromium.googlesource.com/chromium/src/+log/52.0.2724.0..52.0.2725.0?pretty=fuller&n=10000

Suspecting: r391575

Note: 1. Unable to Sign in to chrome in Chromium builds, hence providing suspect from Changelog URL.




 
Expected_History.mp4
2.9 MB Download
Actual_History.mp4
2.3 MB Download
Labels: ReleaseBlock-Beta
Adding Release Block as this is a recent Regression. Please remove if not required.
Thank You.
Cc: ashej...@chromium.org
@calamity: Hey, would you mind checking the above issue as per above details ?

I really appreciate your help.


Thank you!
Cc: tkonch...@chromium.org
Able to reproduce the issue on chrome version canary 52.0.2738.0

calamity@, Could you please take a look 
Cc: dbeam@chromium.org tsergeant@chromium.org
Labels: -ReleaseBlock-Beta
Bugs that are behind feature flags should not be Release Blockers.

Issue is not limited to newly signed in profiles. Easiest repro is to open chrome:history and then middle click the refresh button to load a new history page in the background. Repro still seems to be flaky, switching around to different profiles might trigger it.

It looks like the resize event isn't firing when the page is first shown. Resizing the window after render fixes the problem.

I feel like adding a requestAnimationFrame(function (){ ironList.render() }) somewhere might fix the issue. Any thoughts Tim?
For me, (Linux 52.0.2729.3) when I middle click the refresh button, wait a second and then switch to the new tab, I see a second of the blank empty item, and then the content loads in correctly.

I'd rather try and figure out a real solution than hack in something to the side.

Something to consider: does this happen when you disable async on the app.html bundle?
Project Member

Comment 6 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Proj-MaterialDesign-WebUI
Status: WontFix (was: Assigned)
I think something fixed this a while ago. Please reopen this if you can still reproduce it.

Sign in to add a comment