What else can become a region besides an element? If there aren't too many interfaces, we can just copy/paste this stanza into each IDL, like we do for EventTarget. If there are a lot of them, then I agree that you'll probably want a fancier Supplemental feature.
One way to approach that is to make the [Supplemental] attribute take a list of interfaces. That should be straightforward to implement given our current implementation of Supplemental. Adam On Thu, Jul 19, 2012 at 9:58 AM, Andrei Bucur <abu...@adobe.com> wrote: > Hello Adam, > > Sure: > http://www.w3.org/TR/2012/WD-css3-regions-20120503/#the-region-interface > > The spec does not explicitly states that the Region should be supplemental, > however after raising some issues on www-style ( > http://lists.w3.org/Archives/Public/www-style/2012Jul/0251.html ) and > talking them through (offline) it seemed the best way to solve them was > making Region supplemental for Element and any other object that could > become region. Right now, I'm feeling out the situation to see how feasible > this is to be implemented in WebKit. > > Andrei. > > From: Adam Barth <aba...@webkit.org> > Date: Thursday, July 19, 2012 7:31 PM > To: Andrei Bucur <abu...@adobe.com> > Cc: Kentaro Hara <hara...@chromium.org>, "webkit-dev@lists.webkit.org" > <webkit-dev@lists.webkit.org> > Subject: Re: [webkit-dev] About WebIDL supplemental interfaces > > Can you say what specifically in the CSS regions spec is giving you trouble? > > Adam _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev