make arguments a function prototype property

[rbri]

This is the second step in the arguments refactoring to bring the arguments handling closer to the spec.

• we have some test cases containg // todo; these todo marks the real world expectation

[aardvark179]

This confused me for a minute because Function.prototype.arguments is one thing that really isn't in the spec, but I see what you're doing, and I'm happy to see things move in this direction.

[rbri]

@aardvark179 as mentioned in our meeting I spend my whole time hunting for this regression HtmlUnit/htmlunit#1064. My current assumption is a problem with the caller property being visible to some functions because it is NOT defined on the function prototype but instead on every function.
Had a hard time to understand, that only the move of the 'argument' property is more or less simple. For the 'caller' we have to rethink the activation support and other stuff. Therefore I decide to let this in core-js for the moment.

The good news: after the move of the 'arguments' property we are a bit more closer to the browsers. And after I have applied this PR to my fork, I was able to change the way the caller property is implemented also (HtmlUnit@88a343c).

And with this changes, I got a detailed test suite of 'caller' tests working HtmlUnit/htmlunit-core-js@8769e0e; also some more plain HtmlUnit tests are now passing.

Next step is to check with the jenkins folks, if this solves the problem.... but this is something for the next days.

[andreabergia]

What is supposed to happen here, that there is a todo for it, I wonder...? 🙂

[rbri]

throw ScriptRuntime.typeErrorById("msg.op.not.allowed");

is called far to many times (i guess), i have to check if we can have it as static function

[rbri]

Jenkins is happy with this - HtmlUnit/htmlunit#1064 (comment)