W3C home > Mailing lists > Public > www-style@w3.org > February 2012

Re: [css3-regions] Suggestions for CSS OM Changes

From: Vincent Hardy <vhardy@adobe.com>
Date: Mon, 27 Feb 2012 18:34:49 -0800
To: David Hyatt <hyatt@apple.com>
CC: Mihnea-Vlad Ovidenie <mihnea@adobe.com>, "www-style@w3.org Style" <www-style@w3.org>
Message-ID: <5DAD048A-A1B7-4633-BD9B-0E130E10CD62@adobe.com>
Hi David, Mihnea,

On Feb 27, 2012, at 12:56 PM, David Hyatt wrote:

> On Feb 27, 2012, at 2:20 PM, Mihnea-Vlad Ovidenie wrote:
> 
>> 
>> Right now the NamedFlow interface does not expose the regions associated
>> with the flow, so we should probably add something like:
>> 
>> readonly attribute NodeList regions;
>> 
>> 
>> As with other NamedFlow collections, this one would also be a live
>> collection.
>> 
>> Cheers,
>> Mihnea Ovidenie
>> 
>> 
> 
> Ah, I assumed it did! Yeah, that would be necessary for the changes I suggested. We might ultimately need a Region interface that doesn't depend on Node though, especially if anonymous regions end up becoming commonplace. This is one of the reasons I think we need to think about this stuff a bit more.
> 

What about we do the following:

a. Make the current supplemental interface in '6.2' be a 'Region' interface
b. Make NamdeFlow.getRegionsByContentNode return a list of Regions instead of  a NodeList. If the region happens to be an element, it will just implement the Region interface.
c. add the regions attribute as Mihnea suggests on NamedFlow, but make that a Regions list, not a NodeList.

That would keep the 'regionOverflow' attribute and the getRegionFlowRanges on the 'Region' interface and it would have the advantage of working with elements and pseudo-elements alike (e.g., if the region is '::before' or a ::slot mechanism when we define one to create regions).

Cheers,
-v
Received on Tuesday, 28 February 2012 02:35:18 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:51 GMT