Consider the following test case: var expected = false; var array = new Array(2); array.shift(); var actual = array.hasOwnProperty(0); if (actual !== expected) print("BAD"); Currently it prints BAD when run against jsshell as Array.prototype.shift treats holes or non-existing properties as properties with value "undefined" in disagreement with ECMA-256 188.8.131.52.
Comment #1 is test result on MS Win-2K.
OS: Linux → All
Hardware: PC → All
(In reply to comment #3) > The expected result according to ECMA-262 v3 should be 1/false,false as > non-existing properties Oh, sorry for my misunderstanding of the problem and spam comments.
Fixed as part of the patch for bug 322135.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
Checking in regress-345961.js; /cvsroot/mozilla/js/tests/js1_5/Array/regress-345961.js,v <-- regress-345961.js initial revision: 1.1
verified fixed 1.8, 1.9 20060821 windows/mac*/linux
Status: RESOLVED → VERIFIED
Keywords: fixed1.8.1 → verified1.8.1
You need to log in before you can comment on or make changes to this bug.