On Wed, Jul 25, 2012 at 6:00 PM, Sam Weinig <[email protected]> wrote: > > On Jul 25, 2012, at 5:53 PM, Elliott Sprehn <[email protected]> wrote: > > > On Wed, Jul 25, 2012 at 5:13 PM, Alan Stearns <[email protected]> wrote: > >> ... >> >> From the WebIDL side, it's not strictly multiple inheritance. It's merely >> a supplemental interface that more than one object can implement. None of >> the members of the Region interface can clash with any of the members of >> the object that implements it. >> >> Right now Elements can become CSS Regions, but in the future other objects >> will be able to become CSS Regions. As far as I know, the correct way to >> specify this kind of relation is with WebIDL supplemental interfaces. I'd >> rather figure out the correct way to add this WebIDL functionality to >> WebKit now, than put something else into the spec and WebKit that we'll >> have to change later. >> >> > It seems like this should really be a [NoInterfaceObject]. That resolves > the issue of multiple inheritance since you can no longer do instanceof > Region, and I'm not sure why you'd ever want to do that anyway. > > > I agree. >
That doesn't solve the problem. The problem arises from determining what kind of wrapper to create for an WebCore::Region object (e.g., an Element wrapper or a CSSPseudoElement wrapper). It's easy for us to create the proper constellation of prototype objects. Adam
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo/webkit-dev
