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

Issue 654135 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Oct 2016
Cc:
█ tsergeant@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome history search causes signed in devices vs local history to flicker back and forth

Reported by danielaw...@gmail.com, Oct 8 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce the problem:
1. Open Chrome History
2. Enter any search term into top search box and press enter
3. Glitchiness occurs

What is the expected behavior?
The search should complete successfully, and not become confused about the source

What went wrong?
The "Showing history from your signed-in devices." messages flickers in between that and the Local history equivalent, the loading circle remains spinning and never finishes, no results are displayed, and the sections above where it shows your signed in devices is blank.

Did this work before? Yes Latest version 52 before 53, when I used history last

Chrome version: 53.0.2785.143  Channel: stable
OS Version: 6.3
Flash Version: Shockwave Flash 23.0 r0

Attached are all of the problems I can see.
chromeglitch.flv
238 KB Download
chromeglitch.PNG
5.9 KB View Download
chromeloadingglitch.flv
643 KB Download

Comment 1 by tsergeant@chromium.org, Oct 10 2016

Cc: tsergeant@chromium.org
Components: -UI UI>Browser>History
Thanks for the bug report.

The first issue, with the flickering of local vs remote text, was fixed in  issue 648555 .

I haven't been able to reproduce the second issue you mention, where the search seems to never complete.

Comment 2 by danielaw...@gmail.com, Oct 10 2016 

Interesting, even though I was using the latest version of Chrome and had restarted it several times, after completely restarting my computer and restarting Chrome again a few times, it seems to have been solved, even though Chrome didn't update during that time...

Comment 3 by tsergeant@chromium.org, Oct 10 2016

Status: WontFix (was: Unconfirmed)
That's unusual, but without a way for me to reproduce it, there's not much I can do.

Marking this issue at WontFix, feel free to comment here if the problem comes back.
►

Sign in to add a comment