I have a website with a manifest that validates (http://manifest-validator.com/), and files are clearly downloaded since the "progress" event is fired for each file - but, window.applicationCache.status is always 0 (which mean the website does not have a cache manifest). This is in Firefox 11.
This is at first load. When i refresh the page after the manifest is donwloaded, the applicationcache status if first checking, and the idle - which is correct.
Any ideas?
I'm seeing similar results — Firefox still has major issues with applicationCache status and eventing.
I've filed bug 825618 to hopefully get this a little bit more attention again, although I'm seeing a few other similar bugs that should have flagged the problem a long time ago but are still basically unresolved.
Related
I have a couple of video-requests to an s3-bucket. the last two are cached.
Every not cached request had the expected cors-headers:
Once the video is cached, the cors-headers are missing and it comes to the well known cors-policy error:
It's only reproduceable in windows-chrome, everything works fine on my mac.
Does anyone have the same problem? Is it a browser-bug or am I able to set anything in the bucket to prevent this problem?
I updated the source code for my html page on a server, but when I refreshed the page in chrome, it didn't update. Then I tried performing a hard refresh and emptying the cache, but it still didn't work. I also tried opening the page in Firefox, which gave me the updated page, but chrome still didn't update the page for another few minutes.
(I'm using Chrome 63 on Windows 7)
Update: it seems that this problem only happens with small files online of at most 5KB or so.
I figured it out: change the extensions from ".html" to ".php".
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 simple web page running locally on my machine using XAMPP.
When in Chrome and I load the page, the page appears to load fine and appears as expected. The icon in the tab continues to show the spinning "loading" icon though, it never stops.
Using Chrome Developer tools I can see the network tab and there is nothing showing as loading
Also if I use Internet Explorer then the page loads and there is no loading icon.
Any idea why Chrome might think it is still loading something?
I had the same problem and found out it was one of my chrome extensions. I tried loading my site in an incognito page and the loading symbol stopped after the page finished. I went through my extensions to see which were not allowed in incognito and eventually found that it was "Mailto: for Gmail™ 2.4" causing the problem.
For what it's worth after eight years, I had a similar problem where Chrome would not load some images even though they were definitely available, ready, and waiting.
My solution was to close the browser, flushing cookies, history, and all the other internal cruft which had built up over time (using the "Close All & Clean" extension).
Restarting the browser and reloading the page, everything was there, all tickety-boo.
I have no useful theories on why this might've worked but as they say "works for me." Your mileage may vary.
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.