- From: Krzysztof Maczyński <1981km@gmail.com>
- Date: Wed, 17 Sep 2008 22:49:49 +0200
- To: "Robin Berjon" <robin@berjon.com>
- Cc: <www-svg@w3.org>
> What I don't understand is what this "interpreted language"
> provision is supposed to bring.
Well, my most direct interpretation of the current draft would lead to adding the "event" property to the activation object of the implicitly defined function but keeping the arguments object unchanged. Possible in ECMAScript with custom internal [[Call]] property. I suggested instead something like "function(event, evt)" (order reversed to align with WebApps where the second argument is omitted; ECMAScript allows any number of them on calls) but now I think that the best approach is:
function(evt) {
var event = evt
//contents of handler
}
Or the same with "evt" and "event" swapped (again, for better compatibility with WebApps). Actually, why "evt", is it already implemented?
With this there's also less chance to run into trouble when using arguments.callee.
Received on Wednesday, 17 September 2008 21:16:15 UTC