and oh yea: The method doesn't properly escape the characters passed to it. It seems that it escapes quotes (" => \") as expected, but does not escape slashes and/or line breaks (\,\t,\n,\r,\f) which causes an unterminated string error on the JS side. Not to mention any text that already contains escaped characters breaks (example: \" => \\" should be: \" => \\\"). There are 2 (that we can think of) workarounds for this:
Both of these methods seem to work, but the url encoding adds a considerable amount more characters to what we are sending. Thus, reducing the amount of data we can actually send at one time.
Has anyone else dealt with this?
asked Jan 29 '10 at 07:24 PM
I don't see any reason for there to be a limit, so this sounds like a bug to me. Can you file a bug report with an example script which shows the problem, and details on which platforms (browser, OS) you are experiencing the problem on?
answered Feb 04 '10 at 11:01 AM
jonas echterhoff ♦♦
answered Feb 01 '11 at 12:26 AM