W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2016

[Bug 28812] JSON options 'unescape' and 'liberal' prevent use of off-the-shelf JSON parsers

From: <bugzilla@jessica.w3.org>
Date: Fri, 30 Sep 2016 17:41:59 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28812-523-tEaaToJ2kw@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28812

--- Comment #11 from Michael Kay <mike@saxonica.com> ---
Oh dear. I've scanned the CVS change logs, and I think you are right.

The problem is the text in the third rule under the table:

 If the <code>escape</code> option is set to <code>true</code>, escape
sequences
 are retained in their escaped form, whether or not they represent valid
characters.

In the recent bug 29872 I pointed out that this text was not where you might
expect it (in the "escape" entry in the table), and I proposed moving it into
its proper place the table, and applying the same rule to the json-to-xml
function.

But in fact it seems that the rule was a relic of the state of affairs before
the resolution of this bug (28812), and it should have been deleted when the
resolution of this bug was implemented, but it was overlooked because it was
not in the obvious place. 

Unfortunately, rolling this back involves quite a few test cases which it now
appears should not have been changed.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 30 September 2016 17:42:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:02 UTC