I have a trouble with loading images on google chrome.
I am building a web site, i have built it in html.
When i run HTML file directly in browser it loads all files right away.
After splitting file into php files (to include header and footer and to load content on click) and moving to xampp for testing i have realized that images are not loading on google chrome every time.
I have tested HTML files via xampp, i get the same result, images are not loaded in chrome every time.
If i keep refreshing page, images load once, the next time some are loaded, some are not.
It works fine on Microsoft Edge and Mozilla Firefox.
Any solutions for this?
Related
My developer coded the home page coming soon template. before now it was working fine the site was loading up but now it keeps loading.
I have created a screen cast video to clear the issue and share entire page code.
Here is the link Screencast
In Portfolio you have two images (res.png and pizza.png). Loading both of them require 7800ms. Your whole request is nearly 8700ms. (in my current environment/using my network connection). Those two images are 90% of your loading time.
You also have two resources that are required but not there:
cp.png
ff.png
Both of them being in that Portfolio folder.
Loading time
Loading time for res.png
Loading time for pizza.png
Red lines are 404 http responses (Not Found).
I created a local web app that just displays images and PDFs on a loop kiosk style. It has a basic Node.js http back end that feeds file paths to client browsers and the browsers use embed elements to display those files.
The issue is that when the client has run through the files provided and is told to reload chrome (It looks to be chrome that's doing it at any rate...) downloads a _Thumbs.db file. This app is meant to be a full screen kiosk and I would rather not have the downloads bar or any downloads prompt be present while it's running the slideshow.
I have disabled all the options for thumbnails on the windows side, but oddly enough it is a chrome download prompt that is the issue.
Can I prevent these files from being downloaded? If-Not any Idea how I can prevent Chrome from throwing a download prompt up?
Thanks in advance.
using IE11 the time taken to load the javascript and png files is very huge. After disabling addons it was faster but still not as expected. Javascript loading is happening at the begining of the page and this is causing delay in page loading. Does this have anything to do with network?
I have a site which uses justified-gallery (http://miromannino.github.io/Justified-Gallery/). We've had reports from some Mac users that in Safari, some of the photos won't load. I've managed to replicate the issue as well:
When using the console, it shows:
Failed to load resource: The network connection was lost
Upon viewing the error'd image in a new tab, they load fine. These images aren't loaded in ajax or anything, they use a little bit of javascript to work out the best size photo and then load the image using JavaScript.
Here is a link to the page:
https://www.ephotozine.com/gallery
I haven't found anything that yet that points to a particular problem.
So I created this iphone webapp using an HTML5 manifest file to be able to open it offline. The problem is that the 2 javascript files I load stop working as soon as I openthe appin fullscreen mode twice. Let me explain:
it works when you reload it in ios safari
in webapp mode it works fine the first time you open it
the 2e time you open it the javascript loads but does not work. (it intercepts clicks and does that, only the next page doesn't load with ajax the 2e time)
any idea how this is possible. Must i somehow "reset" the javascript file?
I use jquery (first file) and my js file.
When you are loading the second page with ajax, the url for that page must be included in the cache.manifest.
You probably also want to setup your phone to go through a proxy like Charles http://www.charlesproxy.com/ This will let you see any files that are loaded by the site.
We ran into issues where files were being loaded with cache-busters at the end of the url. Since the cache-busters changed the url, they didn't exactly match what was in the cache.manifest.