If the only problem is to determine the type of JS wrappers, is it possible to <div>make wrapSlow() a virtual method of some base class, instead of static functions?</div><div><br></div><div>It need a tweak on the code generator. Also, it might need to avoid name conflicts </div>
<div>by suffixing like wrapSlowForNode(), wrapSlowForRegion() etc.</div><div><br></div><div>This approach would make wrapSlow() a variation of QueryInterface(). But considering that the functionality is limited and hard to abuse, it might be better than having DOMInterface.</div>
<div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 26, 2012 at 9:53 AM, Alan Stearns <span dir="ltr"><<a href="mailto:stearns@adobe.com" target="_blank">stearns@adobe.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 7/25/12 5:37 PM, "Sam Weinig" <<a href="mailto:sam@webkit.org">sam@webkit.org</a>> wrote:<br>
<div><div class="h5"><br>
><br>
>On Jul 25, 2012, at 5:13 PM, Alan Stearns <<a href="mailto:stearns@adobe.com">stearns@adobe.com</a>> wrote:<br>
><br>
>> On 7/25/12 4:49 PM, "Kentaro Hara" <<a href="mailto:haraken@chromium.org">haraken@chromium.org</a>> wrote:<br>
>><br>
>>>>>>> A) Should we push back on the folks writing the CSS Regions<br>
>>>>>>> specification to avoid using multiple inheritance? As far as I<br>
>>>>>> know,<br>
>>>>>>> this is the only instance of multiple inheritance in the platform.<br>
>>>>>>> Historically, EventTarget used multiple inheritance, but that's<br>
>>>>>>>been<br>
>>>>>>> fixed in DOM4 [4].<br>
>>><br>
>>> If it is possible to avoid the multiple inheritance, that would be<br>
>>>best.<br>
>><br>
>> From the WebIDL side, it's not strictly multiple inheritance. It's<br>
>>merely<br>
>> a supplemental interface that more than one object can implement. None<br>
>>of<br>
>> the members of the Region interface can clash with any of the members of<br>
>> the object that implements it.<br>
>><br>
>> Right now Elements can become CSS Regions, but in the future other<br>
>>objects<br>
>> will be able to become CSS Regions. As far as I know, the correct way to<br>
>> specify this kind of relation is with WebIDL supplemental interfaces.<br>
>>I'd<br>
>> rather figure out the correct way to add this WebIDL functionality to<br>
>> WebKit now, than put something else into the spec and WebKit that we'll<br>
>> have to change later.<br>
>><br>
>> Thanks,<br>
>><br>
>> Alan<br>
><br>
</div></div>>What other objects do you envision implementing CSSRegion? With the spec<br>
>written the way it is now, I see no reason to make anything virtual, or<br>
>even have a Region class. Just implement it in Element. If need to pull<br>
>things out for code reuse purposes, we can do that when it comes to that,<br>
>but right now, there doesn't seem to be a need to complicate things.<br>
><br>
>-Sam<br>
><br>
<br>
I have an upcoming proposal for a CSSPseudoElement object. You can make a<br>
pseudo-element like ::before or ::after into a CSS Region right now in<br>
WebKit. All that's lacking is a way to access those pseudo-elements from<br>
script.<br>
<div class="HOEnZb"><div class="h5"><br>
Thanks,<br>
<br>
Alan<br>
<br>
_______________________________________________<br>
webkit-dev mailing list<br>
<a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br>
<a href="http://lists.webkit.org/mailman/listinfo/webkit-dev" target="_blank">http://lists.webkit.org/mailman/listinfo/webkit-dev</a><br>
</div></div></blockquote></div><br></div>