I am building a simple webpage (http://www.riffomonas.org/reproducible_research/) using Jekyll that is taking a long time to load on Safari. On Firefox and Chrome it loads instantly. In Safari, when I go in to the Web Inspector, it has two errors. The first...
Failed to load resource: The request timed out
The resource it was trying to get is http://api.pubpeer.com/v2/pubposts?filter=doi&devkey=PubMedSafari.
The second...
TimeoutError (DOM Exception 23): The operation timed out.
It's indicating that it was trying to access PP.js
The weird thing to me is that neither the API link or the Javascript are referenced in the code or the rendered HTML.
Any suggestions?
It turns out that the problem was the PubPeer Safari extension, which they are no longer supporting. Once I removed the extension everything worked great.
Related
Click Me
This used to work as a valid href attribute but it seems in the past few months it now shows an error in the console (I'm using Chrome):
Not allowed to load local resource: view-source: http://stackoverflow.com
I found some links from 2013 where this was once a bug in Chrome but said it was fixed.
Could someone point me to an authoritative source that can explain why this no longer works? I assume that this is security by the browser and not an angular issue (since view-source is whitelisted and used to work)
Looks like Chrome and Firefox (at least) disabled this within the past year or so
I found this thread, and these release notes explaining why and provides a timeline as to when the change took place.
Related StackOverflow question: File URL "Not allowed to load local resource" in the Internet Browser
Chrome responds with the "Not allowed to load local resource:" as a security protocol. I'm not sure why this used to work, but not now, though there is no real way around this unless web-security is disabled. There may be a different outcome on other browsers, but ultimately you are correct in thinking that it's Chrome's security.
The reason is that Chrome tries to preload URLs in background, to speed up your browsing experience.
If you open the DevTools after loading the page, the content of the items listed on the Resources tab may not be populated. This is also true of network requests on the Network tab. To see the fully populated resources on the Resources tab, first open the DevTools, then refresh the page, or navigate to the desired page with the DevTools open. Now select the html resource and it should be populated.
The same application that I am developing works fine on Firefox but not on Chrome.
My application a day ago printed some things on the console, but I removed them today, which means that the actualized version of the application does not print anything on the console.
On Firefox it works, everything renders and there is not prints on the console.
However on Chrome, the app still prints on the console. It means that it is retaining some old state for some reason.
Does that even make sense? The code is already gone (erased), so the only way Chrome is printing the old state on the console is if he is storing it.
On Chrome I also get errors of undefined functions, but they are defined. On Firefox that does not happen.
Have you tried reloading the page? Another thing to try to really get rid of the state that the browser is obviously holding onto is to clear the browser cache.
I have a page - quite complex, lots of resources etc.. but it all loads without problems.
However, Google Chrome shows that little "loading" animation in the tab, and there's the "Waiting for (IP)..." bubble in bottom left of the page.
Everything is loaded, as confirmed by developer tools.
Sometimes, I get this in Console, but not always:
Failed to load resource: net::ERR_NETWORK_CHANGED
Failed to load resource: net::ERR_CACHE_MISS
Firefox loads it without problem.
What can be the problem?
(sorry, it's on intranet and I'm not allowed to make it accessible - so just in case you encountered similar issue)
Chrome console tells you what line in the parsed file JavaScript syntax errors are located. Every once in a while, when I click on the link to take me to see the actual code of where the error is, I get a blank screen in the console. If I open up the same page inside Firefox with Firebug, I can see the error code without any issues.
Is this a known error in Chrome? If so, are there any ways to remedy it?
Here is an official list of known issues with Google Chrome. It doesn't seem like that is one of the known issues. I would try again and see if it happens again.
www.mycomputercure.com works fine in all browsers except in IE. In IE it redirects to 404 page after loading the index page briefly. Appreciate any solutions in advance.
Thanks
Just a guess, based on examining the page's network traffic.
Internet Explorer executes HTML Behaviors (HTC files). No other browser does that. Your page has several 404 errors for HTCs. These usually appear right before other requests are aborted and the 404 page shows in IE.
I don't know what logic IE uses for retrieving an HTC file, but perhaps the omission of one purposely (or via a bug) causes the browser to deem the whole page to be "not found".
This thread on Microsoft's site sounds related and suggests other possibilities.
At minimum, start with fixing any 404s caused by the page.