On May 10, 2010, at 10:54 PM, Garrett Smith wrote:
> On Mon, May 10, 2010 at 8:28 PM, Perry Smith <pedz...@gmail.com> wrote:
> <snip>
>> So, how about this?
>>
>> As part of HTMLElement, have a defined bucket, maybe call it elementObject
>> which is defined to be a native ECMAScript object. If X denotes a
>> particular DOM element, then X.elementObject is defined to return the same
>> native ECMAScript object each time. More details could be added perhaps to
>> define how the object is created (i.e. which prototype to use, etc). I'm
>> thinking making it the same as {}.
>>
>
> WebIDL could require DOM objects to be implemented as native ECMAScript
> objects.
To me, the "host objects" and the fact that they are mostly unspecified seems
rather critical and limiting. The getUserData seems terribly awkward and I
guess it suffers from portability issues as well.
Is WebIDL the best place to address this?
Thanks,
pedz
