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

Re: [css-regions] restricting flow-from further

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 10 Jul 2013 13:53:35 -0700
Message-ID: <CAAWBYDD6rNJXfEpRP9QzipGhVGnOgk02yb6qBxW11apvZOYm4Q@mail.gmail.com>
To: Alan Stearns <stearns@adobe.com>
Cc: "www-style@w3.org" <www-style@w3.org>
On Wed, Jul 10, 2013 at 1:20 PM, Alan Stearns <stearns@adobe.com> wrote:
> Hey all,
>
> The flow-from property has until now applied to all non-replaced block
> containers. What qualified as a non-replaced block container wasn't always
> clear to everyone, so I had added a note listing some of what's in and
> what's out (block, inline-block, table-cell, table-caption, and list-item
> - yes. grid or flexbox - no).
>
> The inclusion of table-caption and list-item were a definitional
> side-effect. I'm not aware of any strong use cases for turning these into
> CSS Regions, and implementing this just because they count as block
> containers seems unnecessary.
>
> So I've changed the 'applies to' line for flow-from to only allow block,
> inline-block and table-cell. I've left in the note that what flow-from
> applies to could be expanded in the future. And I've removed the note
> explaining what counts as a block container.

I'm okay with the table-caption change, but list-item is nothing more
than a display:block element that happens to generate an extra
pseudo-element.  In the Display draft, that's exactly what it is, in
fact.

~TJ
Received on Wednesday, 10 July 2013 20:54:21 UTC

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