| Summary: | RAP application with "standard" client-library variant does not work after 1.5 M1 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Holger Staudacher <holger.staudacher> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P1 | CC: | austin.riddle, fr.appel, tbuschto | ||||
| Version: | 1.5 | ||||||
| Target Milestone: | 1.5 M2 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Holger Staudacher
Created attachment 201994 [details]
Error screenshot
I can reproduce it with deployed Controls Demo in Tomcat. The error is in the new javascript file EncodingUtil.js. Continue with the investigation. Reproducible without deployment with Client-Side Library Variant set to "Standard". The problem is in the special characters \u2028 and \u2029 defined as a keys in the _escapeMap. I think that they should be escaped on the server not on the client, because they lead to an error in the JSON protocol message too. Probably truncateAtZero should be done on the server as well. Fixed in CVS HEAD by creating the string with the problematic characters on runtime using String.fromCharCode. For the issue of the the characters breaking the json-message we will open a new bug. |