[Webkit-unassigned] [Bug 10435] nbsp in javascript causes parse errors

bugzilla-daemon at opendarwin.org bugzilla-daemon at opendarwin.org
Wed Aug 16 16:13:51 PDT 2006


http://bugzilla.opendarwin.org/show_bug.cgi?id=10435





------- Comment #3 from opendarwin.org at bdash.net.nz  2006-08-16 16:13 PDT -------
The question I have is why is the JS file being parsed as latin-1 in the first
case?  (eg, why does this even work?)  Is this for the sake of compatibility? 
I recall that the ECMAScript spec states that characters outside of the range 0
- 128 shouldn't be used in source code outside of comments and string literals,
and that the source should be treated as it were in one of the Unicode
encodings.  Presumably this is impractical in many cases, so we're using the
character set of the including page to determine how to parse the JavaScript
file?


-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list