I have a web page with multiple iframes. In Google Chrome, when I click in one iframe a link to load in another it doesn't start the blue spinner circle on the tab of the browser. That was working until this week and is anoying that if it takes 10 secs to load the user doesn't see it, and think that needs to click on the link again.
Is there a chrome new policy on this or a fix I can use to start and stop the spinner?
I cleaned the browser history with no effect, and the webpage code hasn't change.
This is a change that the Chromium dev team has done on purpose, and are not planning on changing it back:
Here is the discussion where they have essentially said that this is not a bug, and will not be fixed:
https://bugs.chromium.org/p/chromium/issues/detail?id=769803#c8
They've essentially said that it's a feature request. Perhaps if enough people request it, they will change it back?
Related
So I'm working on this web project for school and I use atom as editor and both chrome and opera as my browsers to view my work.
The problem is after few time refreshing the page to view my changes the browser does not respond and keep giving me the same old styling or contents I had on the page, I even had a registration form and every time I refresh it the page goes blank and I need to refresh it again in order to see it and when using chrome to view this same page, a confirmation dialogue pops up, I don't know what the problem is and I was wondering if someone can help me figuring it out. Thanks for your time.
Every time you save your file it auto refresh the page and shows the changed
Atom live server
open your web page in browser and reload by this Shift + Ctrl + R
It will refresh the whole page and show like first time opening.
(or)
check in private window of your browser...
You can see the css is reflected
If its a browser issue: Try Uninstalling and reinstalling chrome.
Check to make sure your looking at the right directory, many developers including myself make the mistake of looking at the wrong code base.
If there are a lot of sites on a Chrome tab, a site on the tab that is compute or graphics intensive - say a page with panning and zooming animation - will stutter. So how can I remove sites from a tab so that only the intensive site is left?
Try clicking the "x" on the tab to get rid of it. If it's really stuttering, which I've seen happen on a number of occasions, try Ctrl+W to close the tab. If it gets particularly bad, Alt+F4 will close Chrome. You can then reopen Chrome and manually reopen whichever tabs you just lost that you want to see.
WebGL does not work in the following three scenarios:
(for the 'test webgl' site used get.webgl.org)
1 Start chrome, Google search for the 'test webgl' site, click on the link in the search result.
2 Go to the 'test webgl' site from a link in an email.
3 Start Chrome from a short cut or command prompt, "C:\Program Files\Google\Chrome\Application\chrome.exe" http://get.webgl.org/
This only happens when Chrome is not already running. In other words WebGL does not work when chrome starts up. However it does work if chrome is already running.
The best demonstration is scenario number 3, above. This starts chrome and goes to http://get.webgl.org/ and Webgl does not work. Then do exactly the same again but this time with chrome already open and Webgl works.
Would very much appreciate feedback or a solution, thanks.
Have also created various test sites in html, javascript and webgl, in order to find a work-around. For example if webgl is not available then allow the user to click on a link to open the page in a new tab, this does not work. However if the user opens a new tab then loads the page, webgl is detected and works.
In short, if a customer opens chrome and searches for your website (that has webgl content). Then clicks on the link, webgl will not work. It does not seem reasonable to then instruct the customer to open a new tab and then go to the same website a second time. So far have not been able to find a solution so that it just works without the customer having to fiddle around.
I realize that this may be a chrome issue as it does not occur in firefox, however am trying to find a javascript solution rather than waiting for chrome developers to fix it.
Thanks for any suggestions.
(Windows XP Pro, Chrome V36)
Hi Mack,
Thanks for your reply. The majority of visitors to my web site have XP and Chrome. I should imagine that this is true for quite a lot of peoples, websites.
Problem 1 The first fallback I had on my website was to detect if webgl is supported. If yes then continue as normal. If no then display a help page. This was simple and worked, however, google crawlers do not handle the javascript very well, therefore always index the webgl help page, rather than the home page.
Solution 1 Managed to fix this by having a popup box appear when webgl is not supported, giving the user a choice of whether to continue or go to the help page. The conditional code that processes the user response is arranged so that if the user is a google crawler then it simply 'falls through' and displays the html content of the home page, and not the help page.
There are lots of web sites that seem to have this same problem, including get.webgl.org, in other words, if you do a google search for a website, and that site contains webgl detection and fallback code, the search result always shows the fallback content, rather than the authors intended main content.
Problem 2 Now that I finally have the home page listed correctly by google, found that am still losing many customers, as they are starting chrome, searching google for my site 'suit yourself shirts', clicking the link in the result and being told incorrectly that webgl is not supported.
Am very interested in your solution but do not quite understand how it works. Have tried detection then page refresh or load the page in a new tab or display a link for the user to load the page, but none of these methods seem to work. Seems like quite a fundamental problem that would effect many webgl websites. Would be very greatfull if you could explain your suggestion a little further. Thanks for your help, kind regards - Gary
I am using the malihu custom scroller on a website, and I can not figure why it doesn't react the same way in the demo and on my website.
demo
website
Steps :
Scroll down one custom scroller (doesn't matter how much)
Go to another website or click on a link
Hit the 'Back' button
Demo : goes back to where it was.
Website : goes back to top of list
Deactivating the custom scroller plugin solve this specific issue.
Any idea why?
I tested this on the following browsers:
IE9
Chrome 35
FF 30 (Same as OP)
As the OP said, this only works on FF.
FF has a feature called Back-Forward Cache which remembers the entire state of the page, even the js states. This occurs for the duration the browser stays open. You can read more about it here.
If you don't want to have this occur for experience reasons, there are other posts about it on stackoverflow.
Update
If you read the documentation for the Back-Forward Cache, it states that it won't work if you have the Cache-Control: no-cache response headers, which you do have enabled.
This is causing the browser to get fresh data each time instead of caching images and pages locally for faster browsing on later visits.
I'm having a very strange problem with a site in Google Chrome:
When I click on a link (from a list view to a detail page), the page hangs and I Chrome throws up a dialogue asking me to kill the page. The page is never displayed.
But if I navigate directly to the page, it loads in Chrome without any problems. Both actions (clicking on a link or navigating to the page) work fine in Safari and Firefox.
Disabling "Predict network actions to improve page load performance" in Chrome's settings seems to fix the problem, but this is not a viable solution as I don't have any control of my user's browser settings.
Some more detail about the situation:
The link is just a regular <href>. I'm not doing any javascript
click() handling or anything else. I'm not using any 'prefetch' or 'prerender' <link> elements.
The pages all validate using the W3
html5 validator.
The page I'm navigating to loads a lot of JS, uses Knockout.js for rendering and loads a video file over HTTP.
On the occasions that the page does load (after a very long wait),
Chrome appears to have rendered the entire page in the background and
loaded all external resources. If I navigate directly to the page it
doesn't preload anything though (I'm using knockout to show a 'please
wait' message while the external resources load).
When I log the network requests using Charles, it appears that
Chrome loads the HTML for the page instantly, but the requests for
the external resources seem to take forever.
If I look at the CPU usage in Activity Monitor, 'Google Chrome Renderer' uses 100% CPU when loading from the href, but only 30% when loading directly from the page.
I'm using the latest version of Chrome (22.0.1229.94)
So - my question
Is there a way to programatically disable "Predict network actions to improve page load performance"?
Or is there some other solution to this problem?
Just going through high voted unanswered questions I came across this one, and I once got into a similar situation for entirely different reasons (chrome was preloading a huge file I couldn't afford to load for every user). The fairly simple solution I applied back then was to open the link through Javascript rather than a simple href which worked wonders. Either way, your problem might already be solved, but seeing the number of views I thought I could at least share this small insight.