archives

« Bugzilla Issues Index

#160 — Case of hex digits in evaluation of JSON.stringify("\u000E") isn't precisely specified

• bug_id: 160
• creation_ts: 2011-07-20 17:17:00 -0700
• short_desc: Case of hex digits in evaluation of JSON.stringify("\u000E") isn't precisely specified
• delta_ts: 2011-07-25 16:16:44 -0700
• product: Draft for 6th Edition
• component: technical issue
• version: Initial draft July 12, 2011
• rep_platform: All
• op_sys: All
• bug_status: RESOLVED
• resolution: FIXED
• bug_severity: enhancement
• dependson: 81
• everconfirmed: true
• reporter: Allen Wirfs-Brock
• assigned_to: Allen Wirfs-Brock
• cc: jwalden+beo

---

• commentid: 358
• comment_count: 0
• who: Allen Wirfs-Brock
• bug_when: 2011-07-20 17:17:52 -0700

+++ This bug was initially created as a clone of Bug #81 +++

Per spec which is correct behavior?

assert(JSON.stringify("\u000E") === '"\\u000E"');
assert(JSON.stringify("\u000E") === '"\\u000e"');

The spec says this: "Let hex be the result of converting the numeric code unit value of C to a String of four hexadecimal digits." That seems to permit either -- but why do so? It's harder to test, and I can't think of a good reason why implementations could want to make different choices here.

Every browser I can test escapes to lowercase hex, so it seems best to require the produced hexadecimal digits to be lowercase.

I originally raised this on the es5-discuss list:

https://mail.mozilla.org/pipermail/es5-discuss/2011-March/003963.html

...receiving the response, "Unintentional under specification. You should file a bug at bugs.ecmascript.org":

https://mail.mozilla.org/pipermail/es5-discuss/2011-March/003964.html

---

• commentid: 381
• comment_count: 1
• who: Allen Wirfs-Brock
• bug_when: 2011-07-25 16:16:44 -0700

corrected in editor's current draft