G
Garth17
This totally surprised me. I'm using IE 6.
I built a really simple test.aspx page that had a javascript block in
it like this:
<script language=javascript src="spanish.js"></script>
Inside the spanish.js I had 1 line that set a variable to a spanish
character.
var Test = "á";
When the browser loaded the page it gave an Unterminated String
Constant Error.
Now if I instead create the file as an .htm. IE will not spawn the
error.
Also if I replace with:
<script language=javascript >var Test = "á";</script>
in the .aspx file I will not get the error.
Any Ideas?
Why would IE treat javascript src files different when loading them
from .aspx or .htm page? It is the same client side code.
Is asp.net telling IE something that makes it handle international
characters differently on the client side?
I built a really simple test.aspx page that had a javascript block in
it like this:
<script language=javascript src="spanish.js"></script>
Inside the spanish.js I had 1 line that set a variable to a spanish
character.
var Test = "á";
When the browser loaded the page it gave an Unterminated String
Constant Error.
Now if I instead create the file as an .htm. IE will not spawn the
error.
Also if I replace with:
<script language=javascript >var Test = "á";</script>
in the .aspx file I will not get the error.
Any Ideas?
Why would IE treat javascript src files different when loading them
from .aspx or .htm page? It is the same client side code.
Is asp.net telling IE something that makes it handle international
characters differently on the client side?