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

Re: [css3-regions] Regions as non-replaced block containers

From: Alan Stearns <stearns@adobe.com>
Date: Tue, 19 Jun 2012 16:57:34 -0700
To: "www-style@w3.org" <www-style@w3.org>
CC: Mihnea-Vlad Ovidenie <mihnea@adobe.com>
Message-ID: <CC065443.11EC2%stearns@adobe.com>
On 6/8/12 5:42 AM, "Mihnea-Vlad Ovidenie" <mihnea@adobe.com> wrote:

>The CSSRegions spec details that, for now, only non-replaced block
>containers can become regions:
>http://dev.w3.org/csswg/css3-regions/#the-flow-from-property. Taking a
>look at
> the possible values for 'display' property, I would say that only {
>block, inline-block, compact, run-in, table-cell, table-caption,
>list-item} qualify for making a region. Did I miss any value here? Does
>it make sense to support all the above values for regions,
> like 'compact' for instance?

I do not think it makes sense to support either 'compact' or 'run-in' for
regions. Both of those values can result in inline-level elements in some
cases. I think it makes sense to support all of the others.

I've added this note to the spec as an implementation FYI:

  At the time of this note-writing,
  the display values that always result
  in a block container include block,
  inline-block, table-cell,
  table-caption, and list-item.
  All of these display values
  work as regions with
  non-replaced elements.


Received on Tuesday, 19 June 2012 23:58:06 UTC

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