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

bugzilla-daemon at opendarwin.org bugzilla-daemon at opendarwin.org
Sun Sep 3 08:43:39 PDT 2006


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


ap at nypop.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
          Component|JavaScriptCore              |Page Loading
         Resolution|                            |INVALID




------- Comment #4 from ap at nypop.com  2006-09-03 08:43 PDT -------
(In reply to comment #2)
> Firefox behaves exactly like Safari; would be nice to check WinIE, just in
> case.

  WinIE also chokes when opening this site with encoding set to UTF-8. So, this
is neither a bug nor an incompatibility in WebKit, closing as INVALID.

(In reply to comment #3)
> using the character set of the including page to determine how to parse 
> the JavaScript file?

  Yes, that's done for all kinds of textual subresources. And if it weren't
(this behavior causes external scripts to be misparsed when the main server
does browser sniffing to provide Mac-encoded content, and the server hosting
the script doesn't), we'd use the default browser encoding.


-- 
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