Closed
Bug 489326
Opened 15 years ago
Closed 5 years ago
EcmaScript, 5th Edition tracking bug
Categories
(Rhino Graveyard :: Core, defect)
Rhino Graveyard
Core
Tracking
(Not tracked)
RESOLVED
INACTIVE
People
(Reporter: rspeyer, Assigned: norrisboyd)
References
()
Details
User-Agent: Opera/9.64 (Macintosh; Intel Mac OS X; U; en) Presto/2.1.1 Build Identifier: Rhino 1.7 release 2 2009 03 22 A bug to track the progress of making the Rhino implementation conform to the EcmaScript 5 spec (formerly EcmaScript 3.1). Reproducible: Always Including: - Updating the Object property attributes to Enumerable, Configurable, Writable - Add the new methods to Object - Add the new methods to the other built-ins - Add the JSON object - Update the parser to allow specifying property attributes in object literals - more...
Comment 1•15 years ago
|
||
Whats the difference between this bug and Bug 445494?
Comment 2•15 years ago
|
||
@TNO That bug is the SpiderMonkey es5 tracking bug, this one is the Rhino es5 tracking bug.
Comment 3•12 years ago
|
||
Check out [1] for a more ECMAScript5 compliant Rhino version, mainly focusing on test262 conformance. As of speaking only seven test cases from test262 still fail. [1] https://github.com/anba/rhino/tree/es5-test262
Comment 4•12 years ago
|
||
André: Wow, this is a massive contribution! Thank you! What is your feeling about merging this into the 1.7R4 release which should be out soon? Any commits that may be risky?
Comment 5•11 years ago
|
||
Indeed,kudos André (and hello!). It would be wonderful to see your improvements incorporated into Rhino.
Comment 6•5 years ago
|
||
Closing. Bug management is now done here:
https://github.com/mozilla/rhino
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•