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

Re: [css3-regions] Improve the NamedFlow JS interface

From: Andrei Bucur <abucur@adobe.com>
Date: Mon, 25 Jun 2012 15:19:43 +0100
To: Alan Stearns <stearns@adobe.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <CC0E418E.35A3F%abucur@adobe.com>
I've been looking for something similar to what I imagine that exists
today and I think this is it:

The HTMLCollection has both an index getter for easy iterations and a name
getter for direct access to the item. Can we extend this mechanism for the


On 6/21/12 11:18 PM, "Alan Stearns" <stearns@adobe.com> wrote:

>On 6/21/12 8:36 AM, "Andrei Bucur" <abucur@adobe.com> wrote:
>>I've been reading the thread [1] on the public-webapps list and I was
>>wondering if anyone came up with a common use case for enumerating all
>>NamedFlows in a Document. If not, I would like to re-propose making the
>>namedFlow collection indexable by name.
>>As long as there's a way (e.g. using Object.keys()) to iterate through
>>NamedFlow objects, I think it's more intuitive for a JS developer to see
>>the collection as a map. Having both a getter function (getFlowByName())
>>and the collection attribute (namedFlows) seems confusing (questions like
>>"Which one should I use?" or "What's the point of that collection?" come
>>in my mind). Unifying the two APIs looks like a good option to me.
>Are you suggesting we replace the NamedFlowCollection with a NamedFlowMap
>as Tab proposed?
>Or are you suggesting we change the NamedFlowCollection getter to take a
>string argument instead of an index, and remove Document.getFlowByName()?
Received on Monday, 25 June 2012 14:20:18 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 February 2015 12:35:11 UTC