Not loading pages in new tabs first time |
|||||
Issue descriptionChrome Version: 56.0.2924.18 (Official Build) dev (64-bit) OS: OSX 10.11.6 What steps will reproduce the problem? (1) Load a page in a new tab - either by clicking a link, or opening a new tab and typing a URL (2) Wait. Nothing happens. Note that the loading indicator/button (between forward and home buttons) is the 'reload' one, not the 'X' one. (3) Click reload once. Or maybe twice. Then the page loads. What is the expected result? Page loads first time What happens instead? I have to click reload once or twice. Please use labels and text to provide additional information. This is weird and intermittent. I don't have good repro steps. However, it's been happening to me enough that I'm reporting a bug. I thought maybe it only happened for Google internal URLs, but I had it just then when I tried to load a user's Twitter page. In this case, I clicked a link which opened a new tab, and it just sat there.
,
Dec 12 2016
I've been seeing similar behavior on 55.0.2883.75; wondering if it might be some corp extension we all have installed, given the version mismatch.
,
Dec 14 2016
It's a good thought about corp extension - I have only seen this on my corp Mac (but I only run dev/canary on these devices :) ). I've also been seeing it for a while, but was only recently convinced enough that it was a real problem to file a bug.
,
Dec 20 2016
Changing component to extensions for them to look at.
,
Dec 22 2016
I'm seeing this on my personal MacBook Pro where the Chrome Sync account is my personal account (although my corp account is one of three Google accounts signed in in the content area). Still seeing this pretty reliably, still on 56.0.2924.21 (Official Build) beta (64-bit)
,
Jan 13 2017
I don't think this is a problem in the extensions platform, which is what Platform>Extensions is for, so removing that component. Maybe it's a corp extension, but #5 implies perhaps not...
,
Jan 10
Archiving P3s older than 1 year with no owner or component. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by komoroske@chromium.org
, Dec 12 2016