I've created an issue with attached patch to implement new feature Context.FEATURE_NON_ECMA_TO_BOOLEAN: https://bugzilla.mozilla.org/show_bug.cgi?id=412247
Can a Rhino committer look at it? This would allow HtmlUnit (as well as other projects using Rhino to simulate a browser) to correctly handle document.all boolean conversion. Cheers, Marc. -- Blog: http://mguillem.wordpress.com Marc Guillemot wrote: > Hi, > > in HtmlUnit I need to simulate Firefox results for following > (document.all being a custom host object): > > document.all ? true : false // -> false > Boolean(document.all) // -> true > > It seems to me that I can't do that with current Rhino state: Rhino > handles boolean conversion the same way in both above cases, and unless > language version is set < 1.3, getDefaultValue is not called on the object. > > Is this correct? Is there an other way to handle this? > > Cheers, > Marc. _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
