Closed Bug 423580 Opened 16 years ago Closed 6 years ago

[builtins ES3 parity] Number is not according to ES3 nor ES4

Categories

(Tamarin Graveyard :: Virtual Machine, enhancement)

Product:
Tamarin Graveyard
Component:
Virtual Machine
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX
Milestone:
Future

People

(Reporter: lhansen, Unassigned)

References

Details

From SpiderMonkey test suite: (new Array(new Number(0))).length yields 0 but should yield 1 because a Number object is not a 'Number' in the sense handled specially by the Array constructor, see E262-3 15.4.2.2.
Summary: [builtins] Number is not according to ES3 nor ES4 → [builtins ES3 parity] Number is not according to ES3 nor ES4
Also, !(new Number(0)) should yield false (object converted to boolean is true) but yields true (0 converted to boolean is false).
Severity: normal → enhancement
OS: Windows XP → All
Hardware: x86 → All
Flags: in-testsuite?
Flags: flashplayer-triage+
Flags: flashplayer-qrb?
Blocks: ecma-incompatibility
Flags: in-testsuite?
Flags: flashplayer-qrb? → flashplayer-qrb+
Priority: -- → P3
Target Milestone: --- → Future
Priority: P3 → --
Tamarin is a dead project now. Mass WONTFIX.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Tamarin isn't maintained anymore. WONTFIX remaining bugs.
You need to log in before you can comment on or make changes to this bug.