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

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

From: Alan Stearns <stearns@adobe.com>
Date: Thu, 21 Jun 2012 13:18:25 -0700
To: Andrei Bucur <abucur@adobe.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <CC08CD2E.120F7%stearns@adobe.com>
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 the
>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 the
>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 Thursday, 21 June 2012 20:18:58 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:00 UTC