archives

« Bugzilla Issues Index

#1272 — Incorrect algorithm steps in String.prototype.normalize

• bug_id: 1272
• creation_ts: 2013-03-08 15:23:00 -0800
• short_desc: Incorrect algorithm steps in String.prototype.normalize
• delta_ts: 2014-07-27 22:25:30 -0700
• product: Draft for 6th Edition
• component: technical issue
• version: Rev 14: March 8, 2013 Draft
• rep_platform: All
• op_sys: All
• bug_status: VERIFIED
• resolution: FIXED
• priority: Normal
• bug_severity: normal
• everconfirmed: true
• reporter: Norbert
• assigned_to: Allen Wirfs-Brock

---

• commentid: 3400
• comment_count: 0
• who: Norbert
• bug_when: 2013-03-08 15:23:27 -0800

The new String.prototype.normalize function includes an incomplete algorithm step:

4. If form is not provided or undefined.

The strawman had "If form is undefined or not provided, let form be 'NFC'." It seems the entire step has become unnecessary because the function parameter list now provides a default value for form.

The function also has a step that lists "NFC" twice and omits "NFKD" from its condition, and then has two "then" parts for one "if":

7. If f is not one of "NFC", "NFD", "NFKC", or "NFC", then let form be "NFKD", then throw a RangeError Exception.

The statement should be

7. If f is not one of "NFC", "NFD", "NFKC", or "NFKD", then throw a RangeError Exception.

Finally, step 8 contains "by in". Either one of these words fits, but both together are too much.

---

• commentid: 3401
• comment_count: 1
• who: Allen Wirfs-Brock
• bug_when: 2013-03-08 15:34:02 -0800

fixed in rev 15 editor's draft

---

• commentid: 3968
• comment_count: 2
• who: Allen Wirfs-Brock
• bug_when: 2013-05-14 18:14:00 -0700

resolved in rev 15, May 14, 2013 draft

---

• commentid: 9636
• comment_count: 3
• who: Norbert
• bug_when: 2014-07-27 22:25:30 -0700

Verified in rev 26 draft.