[Bug 27477] JSON Serialization

• From: <bugzilla@jessica.w3.org>
• Date: Mon, 01 Dec 2014 17:56:16 +0000
• To: public-qt-comments@w3.org
• Message-ID: <bug-27477-523-ZVuT5U8s1d@http.www.w3.org/Bugs/Public/>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27477

--- Comment #1 from Christian Gruen <christian.gruen@gmail.com> ---
Two more observations:

* Serialization-json-40:

Wouldn't "\t\n\r" be a valid result as well? Next, RFC7159 allows the character
sequence in escaped characters to be upper or lower case, so I would recommend
to use the following regex:

  \\u(0009|t)\\n\\u(000D|000d|r)

* Serialization-json-55:

I believe that the output ["&#xD;","\r"] would also be correct. A more flexible
pattern could look as follows:

  \["&amp;(#13|D|d);","\\u(000D|000d|r)"\]

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 1 December 2014 17:56:17 UTC