It seems that they check:
Function.prototype.constructor.prototype.bind
and don't overwrite it if it is already defined.
Rhino accepts to overwrites it without problem. I think that this is
(will be) an incompatibility of MooTools with ES5.
Cheers,
Marc.
Marcello Bastéa-Forte a écrit :
Curious, does MooTools check if Function.prototype.bind exists before
overwriting it? (which might imply a bug/incompatibility in MooTools) Are
there functional differences between ES5 and MooTool's bind functions?
Or does Rhino disallow/ignore overwrites to Function.prototype.bind? (which
might imply a bug in Rhino)
Marcello
On Wed, Aug 19, 2009 at 7:06 AM, Marc Guillemot <[email protected]> wrote:
Norris Boyd a écrit :
What are the elements of ES5 support that block HtmlUnit?
with latest Rhino from Head, the tests of the MooTools library don't pass
anymore. The first (only?) problem seems to be that they define a bind
function on Function.prototype but due to ES5 changes, the built-in bind
function is returned in place of the one defined by the library, when called
on a function.
Cheers,
Marc.
_______________________________________________
dev-tech-js-engine-rhino mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
_______________________________________________
dev-tech-js-engine-rhino mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
