This might well not be fixable. It's caused by us installing the AS3 traits into the normal prototypes for primitive builtins. That leads to Boolean.prototype having definitions for both AS3::valueOf and public::valueOf, and we go for the AS3 version. For some reason that I cannot figure out at all, this is actually not true in the shell: there we correctly resolve to public::valueOf, with the interpreter and both compilers. In the browser, we do the wrong thing always. I'm not sure this matters at all as I have a hard time thinking of any content that would actually depend on this: it should behave the same absolutely everywhere *but* for Boolean.prototype itself.
3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.