Details
-
Type:
Defect
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Environment:Windows 7 x86, MSIE 9, Jetty
Description
the following call: (reader/read-string "{:status :ok}") produces {"\uFFFD'status" "\uFFFD'ok"} which differs from expected {:status :ok}
the server inserts proper content-type (utf-8) header for all javascript files
the problem disappears if unicode special characters are manually replaced with their escaped equivalents ("\uFDD0") in cljs.core.keyword function in the compiled core.js file
it doesn't disappear when call to the str_STAR_ function is replaced to the concatenation operators, which suggest that the function works correctly and adds some mystery to the problem
currently I have no possibility to reproduce the problem on other system, so I'm not certain in all of the aspects
Activity
David Nolen
made changes -
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Duplicate [ 3 ] |
David Nolen
made changes -
Resolution | Duplicate [ 3 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Thomas Scheiblauer
made changes -
Attachment | cljs-133_fix.patch [ 10939 ] |
Thomas Scheiblauer
made changes -
Attachment | cljs-133_fix.patch [ 10939 ] |
David Nolen
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Completed [ 1 ] |
David Nolen
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Keywords in ClojureScript are just JavaScript strings. If you mean that you're seeing this on the client, that is expected, are you saying that you're seeing this in the ClojureScript REPL?