4263 2005-08-01 22:40:55 -0700 Version bug: js1_2/version120/boolean-001.js 2011-06-13 17:10:54 -0700 1 1 1 Unclassified WebKit JavaScriptCore 412 Mac OS X 10.4 RESOLVED WORKSFORME P2 Normal --- 4262 1 ggaren ggaren barraclough digdog ian jhaygood oldest_to_newest 15674 0 ggaren 2005-08-01 22:40:55 -0700 This test fails because it expects new Boolean(false) to return false, as it did in JS 1.2. 34542 1 jhaygood 2006-02-28 21:20:39 -0800 Comparison to other JS engines without having a version set: JS 1.6 (Firefox 1.5.0.1 / Windows) * Returns False JScript 5.6 (Internet Explorer 6 SP2 / Windows) * Returns False Should we follow this old behavior since JScript and JS both do this? 34650 2 ggaren 2006-03-01 09:36:06 -0800 It looks like new Boolean(false) is supposed to return false in JS 1.5: 15.6.2.1 new Boolean(value) The [[Prototype]] property of the newly constructed object is set to the original Boolean prototype object, the one that is the initial value of Boolean.prototype (15.6.3.1). The [[Class]] property of the newly constructed Boolean object is set to "Boolean". The [[Value]] property of the newly constructed Boolean object is set to ToBoolean(value). 44507 3 ap 2006-11-24 23:05:13 -0800 *** Bug 11579 has been marked as a duplicate of this bug. *** 44251 4 digdog 2006-11-26 00:50:43 -0800 The real cause that failed the test was IF statement. var variable = new Boolean(false); if (variable == false) print("EqualityExpression == RelationalExpression will be true"); if (variable) print("RelationalExpression will apply ToBollean operator on this Boolean 'object'"); // js1.2 sample use this, and expect the result of IF statement will be 'false' In the sample above, JSCore and other JS engines are acting the same, both these two IF statements will be true, since 'variable' is a Boolean 'object' not a 'boolean' value, so the second IF statement will apply ToBollean(Object) and return true. If you check js1_3/Boolean/boolean-001.js, you will see they already fixed this issue. (http://bugs.webkit.org/show_bug.cgi?id=11579#c7) 420078 5 barraclough 2011-06-13 17:10:54 -0700 We don't support language versions in JSC (other than strict / non-strict), and al behaviour seems ES5 compliant. I don't think we need change anything here - the test documents our deliberate non-compliance with JS1.2.