- From: Mark S. Miller <erights@google.com>
- Date: Mon, 5 Oct 2009 09:20:26 -0700
- To: Garrett Smith <dhtmlkitchen@gmail.com>, Travis Leithead <travil@microsoft.com>, Allen Wirfs-Brock <Allen.Wirfs-Brock@microsoft.com>, "Mark S. Miller" <erights@google.com>, Doug Schepers <schepers@w3.org>, "public-script-coord@w3.org" <public-script-coord@w3.org>
On Mon, Oct 5, 2009 at 12:54 AM, Cameron McCormack <cam@mcc.id.au> wrote:
> Garrett Smith:
>> > CM: users would like the ability to override a mixin in once place (e.g.,
>> > EventTarget)
>>
>> What does this mean?
>
> Being able to do
>
> EventTarget.prototype.addEventListener = …
>
> instead of doing it on every mixin prototype object, which is how it
> would need to be done as currently specified.
>
>> > TL: IE8 spread the mixins out over the affected objects (duplicating their
>> > definitions)
>>
>> What does this mean?
>
> If IDL said
>
> interface Base { };
> interface Mixin { void f(); };
> interface DerivedOne : Base, Mixin { };
> interface DerivedTwo : Base, Mixin { };
>
> then a property named 'f' would exist in a DerivedOne instance’s
> prototype chain somewhere, and a separate one would exist in a
> DerivedTwo instance’s, as far as I understood it.
I understood the same thing.
> I don’t remember if
> it was mentioned where specifically those properties go.
It was not mentioned specifically. Of course, if mixing-in mixins are
done with the expected copy, the answer would be
DerivedOne.prototype.f and DerivedTwo.prototype.f
> --
> Cameron McCormack ≝ http://mcc.id.au/
>
--
Cheers,
--MarkM
Received on Monday, 5 October 2009 16:36:26 UTC