[webkit-dev] About WebIDL supplemental interfaces
Adam Barth
abarth at webkit.org
Thu Jul 19 12:32:28 PDT 2012
It sounds like you don't have a problem today, but you might have a
problem in the future. I'd recommend going with the simple solution
today and worrying about future problems in the future.
Adam
On Thu, Jul 19, 2012 at 11:04 AM, Alan Stearns <stearns at adobe.com> wrote:
> Adam,
>
> Currently, an Element is the only thing represented in the object model
> that can become a CSS Region.
>
> Pseudo-elements (::before and ::after) can become CSS Regions, but AFAIK
> there isn't yet a representation of those in the OM. I'm hoping this
> changes in the future (I'm working on a spec that addresses this), so that
> could be a second copy. I can construct a region chain now that includes
> pseudo-element Regions, and the NamedFlow interface is supposed to return
> a sequence of Regions from its getRegions() method. So ideally we'd have a
> way of returning a Region interface for those pseudo-elements that have
> been added to the region chain.
>
> Alan
>
> On 7/19/12 10:50 AM, "Adam Barth" <abarth at webkit.org> wrote:
>
>>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 <abucur at 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 <abarth at webkit.org>
>>> Date: Thursday, July 19, 2012 7:31 PM
>>> To: Andrei Bucur <abucur at adobe.com>
>>> Cc: Kentaro Hara <haraken at chromium.org>, "webkit-dev at lists.webkit.org"
>>> <webkit-dev at 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 at lists.webkit.org
>>http://lists.webkit.org/mailman/listinfo/webkit-dev
>
More information about the webkit-dev
mailing list