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

Re: [css-regions] Reworking getNamedFlows()

From: Alan Stearns <stearns@adobe.com>
Date: Tue, 15 Oct 2013 13:12:19 -0700
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: Mihnea-Vlad Ovidenie <mihnea@adobe.com>, François REMY <francois.remy.dev@outlook.com>, "www-style@w3.org" <www-style@w3.org>, "cam@mcc.id.au" <cam@mcc.id.au>
Message-ID: <CE82EF7C.31C03%stearns@adobe.com>
On 10/15/13 10:59 AM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:

>On Tue, Oct 15, 2013 at 10:51 AM, Alan Stearns <stearns@adobe.com> wrote:
>> On 10/15/13 10:43 AM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:
>>>On Mon, Oct 14, 2013 at 3:08 PM, Alan Stearns <stearns@adobe.com> wrote:
>>>> OK, coming back to this. If we go the Map route, then I'm assuming
>>>>it's
>>>>a
>>>> static, read-only map. Would something like this work?
>>>
>>>Is there a particular reason for it to be static?  I assume that the
>>>current spec's interface is live, right?
>>
>> The current spec's interface is a static snapshot, based on the feedback
>> that I get every time I try to define something as live [1]. My current
>> rule of thumb is to assume something should be static unless there's a
>> very good reason to make it live.
>
>All right, that's fine.

OK, the change is checked in [1].

Thanks,

Alan

[1] http://dev.w3.org/csswg/css-regions/#the-namedflow-interface
Received on Tuesday, 15 October 2013 20:12:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:51:03 UTC