I've been working on this site and checking in IE8, Chrome, FF and Safari. Everything has been fine throughout.
However, now that I've uploaded the site to a server, it crashes IE8 every time - what is going on?!
Link: http://www.oxfordsoundhire.com/morland
Please help!!
Link: http://www.oxfordsoundhire.com/morland
It's working on Internet Explorer 10
I think it's to do with this js file: http://www.oxfordsoundhire.com/morland/js/carouFredSel.html
It's not actually at that location, but instead of just returning blank, your server is returning a full 404.html file, and the opening "<HTML..." is making it break.
Related
In vs code everything is fine. While clicking on the GO live button(for HTML CSS files) and its showing port:5500 but when the chrome browser opens after some seconds loading it saying its taking too long to respond This site cant be reached ERROR how to fix it is really a headache for me this is the screen snip of error
I had the same problem before , at first i just ignored the live server extension and i opened my html files directly from the folder . But after , i did a Restart to the extension host and it worked perfectly again .
It seems like a bug in the code causing infinite loop and hence crashing. I believe my solution can help with this perfectly. Please check this link!
I was trying to load this simple video in firefox but when I try to access the video it loads forever and never plays whereas it works perfectly in chrome. It does the exact same thing with every videos I tried. I don't understand why it does not work.
https://www.w3schools.com/html/mov_bbb.mp4
This is how it looks when I try to open it
It is working in firefox, I think you need to update your browser. Check more for documentation on firefox they have details about it.
I have ASP.NET Core web application. The view is using iframe to load PDF file from amazon s3.
<iframe style="width:100%;height:100vh" src="https://xxxx.s3-us-west-2.amazonaws.com/mybucket/a_01_03_44_35_5745663485955446.pdf"></iframe>
The above code was working fine until recently.
Now iframe does not show any pdf. When i check network using F12 it shows Protocol and Result/Description as Pending
if copy the URL and paste it into IE 11 directly then browser shows the file.
The above behavior is happening in IE 11 and IE Edge, as usual chrome works fine.
I am not sure if recent windows update has got anything to do with this.
Update 1
I take it back, I cannot open S3 url in IE 11 or IE Edge directly either.
This has nothing to do with ASP.NET Core. Why don't you load the PDF with HttpClient and serve it through a controller. Could also have the benefit that you can cache it if this is frequently requested. Or better use the AWS SDK.
I have the same problem since the begining of 2017/08. The difference is I cannot open the url directly on IE11 and Edge eigther. The F12 network tab also shows both Protocal and Result/Description as Pending. No problem on Chrome, firefox and safari.
Several PCs in our company started having this problem from the same time.
Here is a sample url
(please open this by IE11 on Windows10).
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.
So I have an interesting quirk that isn't making a lot of sense right now.
I am trying to create drop down menus for a website using CSS.
When I open the index.html file locally, it looks fine in Firefox, and it is all messed up in IE.
When I FTP the file to a server, it looks fine in both Firefox and IE.
I would like to be able to see what it is supposed to look like in IE locally, before uploading it to the actual site.
What would cause IE to render incorrectly on the local file, but correctly on a server?
For some reason, IE9 (and possibly 10, I'm not sure) runs Intranet sites in Compatability Mode, and it defines all locally viewed HTML files as intranet pages. So, when you're accessing local files, you may very well be accessing them roughly as if you're viewing in IE7.
Turning this off has been covered here.