archives

« Bugzilla Issues Index

#225 — Globalization namespace may conflict with existing code

• bug_id: 225
• creation_ts: 2011-11-29 13:34:00 -0800
• short_desc: Globalization namespace may conflict with existing code
• delta_ts: 2012-10-16 15:13:38 -0700
• product: Internationalization - ECMA-402
• component: Specification
• version: Edition 1.0 drafts
• rep_platform: All
• op_sys: All
• bug_status: RESOLVED
• resolution: FIXED
• priority: Normal
• bug_severity: normal
• everconfirmed: true
• reporter: Norbert
• assigned_to: Norbert

---

• commentid: 511
• comment_count: 0
• who: Norbert
• bug_when: 2011-11-29 13:34:04 -0800

Issue raised in the TC39 meeting November 2011: The Globalization namespace may conflict with existing code in JavaScript libraries. A possible solution is to not have a namespace, but instead provide a module loader similar to what's planned for ES6.

Discussion threads start at:
https://mail.mozilla.org/pipermail/es-discuss/2011-November/018560.html
https://mail.mozilla.org/pipermail/es-discuss/2011-November/018600.html

---

• commentid: 697
• comment_count: 1
• who: Norbert
• bug_when: 2012-02-27 20:57:45 -0800

This issue was discussed again in the TC39 meeting January 2012, and the consensus was that the Internationalization API shouldn't become dependent on a module system that's not fully defined yet. We'll therefore stick with a namespace object.

Globalization seems too long to many, and it appears the name was also used in the global namespace by an early version of the library now called Globalize, so we switched to Intl.

The change from Globalization to Intl is included in the spec draft of 2012-02-23.