W3C home > Mailing lists > Public > www-style@w3.org > October 2011

RE: [css3-regions] more API for NameFlow

From: Vincent Hardy <vhardy@adobe.com>
Date: Tue, 25 Oct 2011 18:25:06 -0700
To: "www-style@w3.org" <www-style@w3.org>
Message-ID: <CACCAF82.1E33B%vhardy@adobe.com>
Hi Alex,

This sounds good to me (contentNode instead of content).


Alex wrote:

Just to be clear on what I am proposing: 'content' property is an array of elements containing all elements that have 'flow-into' property applied. It is NodeList because that's how other APIs return element collections (e.g. getElementByTagName<http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-A6C9094>). I would like to not make assumptions that the collection only has elements though. If in the future there is a way to send content of an element to named flow (Issue 19: Special behavior of iframe flow<http://wiki.csswg.org/spec/css3-regions#issue-19special-behavior-of-iframe-flow>) this will still work.

I am trying to think of a more descriptive name... 'content' actually seems intuitive to me, but let's try something else.
It could be NamedFlow.flowSources. Or NamedFlow.flowContent? NamedFlow.contentNodes?

I guess then NamedFlow.getRegionByContentNode() would also be more explicit.

Received on Wednesday, 26 October 2011 01:28:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:06 UTC