Closed
Bug 854049
Opened 12 years ago
Closed 5 years ago
Change access to global object slots for iterators and Intl module objects
Categories
(Core :: JavaScript: Internationalization API, defect)
Core
JavaScript: Internationalization API
Tracking
()
RESOLVED
DUPLICATE
of bug 1288457
People
(Reporter: mozillabugs, Unassigned)
References
Details
Attachments
(1 file)
The implementation of Intl objects (bug 769872) follows that of iterators (bug 725909 and bug 725907) in its pattern of access to global object slots. In bug 769872 comment 17 and bug 769872 comment 20 Jeff suggested a different pattern. I implemented his suggestion in the attached patch, but for consistency the same pattern should also be used for iterators. Note that the patch dates to October 2012, so some bit rot will have occurred. There's more discussion in bug 769872 comment 22, bug 769872 comment 29, bug 769872 comment 62, bug 769872 comment 67.
Comment 1•11 years ago
|
||
Mass-moving existing Intl-related bugs to the new Core :: JavaScript: Internationalization API component.
If you think this bug has been moved in error, feel free to move it back to Core :: JavaScript Engine.
[Mass change filter: core-js-intl-api-move]
Component: JavaScript Engine → JavaScript: Internationalization API
Assignee | ||
Updated•11 years ago
|
Assignee: general → nobody
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•