Kind of feeling itchy since couple of weeks for not being able to find out why javascript or .js files not loading properly for static html file in chrome and firefox, but works absolutely fine in IE.
Ok now used browser debugging tools, IE show the .js files loaded successfully and works fine. But chrome/forefix shows script were loaded like gibberish (chineese,japanese something like that). Something fishy going on, but how would you find it. Ok tried some other static html files and works absolutely fine, but only the html generated using xsl is having the issue.
No luck, then suddenly felt something wrong with file. Ok opened the working file in notepad and have found this file is saved ASCII encoding. Now the buggy file its in unicode that's it.
IE loads all references in the format available by the file, but chrome/firefox tries to load based on the base file (.html file) which has
So modified xsl to output standard utf-8 format and job done.
Never trust anything that can think for itself if you can't see where it keeps its brain.
~J.K. Rowling
Ok now used browser debugging tools, IE show the .js files loaded successfully and works fine. But chrome/forefix shows script were loaded like gibberish (chineese,japanese something like that). Something fishy going on, but how would you find it. Ok tried some other static html files and works absolutely fine, but only the html generated using xsl is having the issue.
No luck, then suddenly felt something wrong with file. Ok opened the working file in notepad and have found this file is saved ASCII encoding. Now the buggy file its in unicode that's it.
IE loads all references in the format available by the file, but chrome/firefox tries to load based on the base file (.html file) which has
m eta http-equiv="Content-Type" content="text/html; charset=utf-16"
So modified xsl to output standard utf-8 format and job done.
Never trust anything that can think for itself if you can't see where it keeps its brain.
~J.K. Rowling