Perhaps @@unscopable shouldn't be a Set...
Erik Arvidsson
erik.arvidsson at gmail.com
Wed Apr 30 11:05:45 PDT 2014
On Wed, Apr 30, 2014 at 1:22 PM, Rick Waldron <waldron.rick at gmail.com>wrote:
>
> On Wed, Apr 30, 2014 at 1:14 PM, Axel Rauschmayer <axel at rauschma.de>wrote:
>
>>
>>
>
>> * Hard-coding `with` to ignore only Array.prototype.values.
>>
>
My main use case for unscopable is for DOM. Today we cannot add nice named
methods to Element or any of its superclasses since HTML attribute event
handlers uses ObjectEnvironments.
>From Web Animation spec
interface Animatable {
AnimationPlayer animate (object? effect, optional (double or TimingInput)
timing);
...
}
Element implements Animatable;
This means that any HTML attribute event handler that tries to call a
global function called animate are now broken.
@unscopable allows us to have nice things.
--
erik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140430/fae0b633/attachment.html>
More information about the es-discuss
mailing list