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

RE: [css3-regions][cssom] NamedFlowCollection as a live collection?

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Thu, 31 May 2012 20:56:07 +0000
To: Mihnea-Vlad Ovidenie <mihnea@adobe.com>, "www-style@w3.org" <www-style@w3.org>
CC: "Anne van Kesteren (annevk@opera.com)" <annevk@opera.com>
Message-ID: <2C86A15F63CD734EB1D846A0BA4E0FC823C9F80C@CH1PRD0310MB381.namprd03.prod.outlook.com>
See http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#collections .

My understanding of HTML conventions is that if collection is an attribute it must be live. Anne - would you say it is "must" or "should" ?

We can of course chose to make any collection static. getRegionFlowRanges() returns a static collection (of live ranges).

Do you have a problem with the collection being live?

From: Mihnea-Vlad Ovidenie [mailto:mihnea@adobe.com]
Sent: Thursday, May 31, 2012 2:35 AM
To: www-style@w3.org
Subject: [css3-regions][cssom] NamedFlowCollection as a live collection?


In the latest version of the CSSRegions spec (http://dev.w3.org/csswg/css3-regions/#the-namedflow-interface), the NamedFlowCollection is described to be a live collection of NamedFlow objects and it is exposed as an attribute on the Document interface. Are there any use cases that require this collection to be live rather than static? Is there a guideline/preferred way to make a collection live vs static when designing the CSSOM API?

Received on Thursday, 31 May 2012 20:57:46 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:59 UTC