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

Re: [css3-regions] New CSS Regions editor draft

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 2 Jun 2011 15:38:14 +1200
Message-ID: <BANLkTi=shZpf8mzbyycSsAbHCeYd=pgwqg@mail.gmail.com>
To: Alex Mogilevsky <alexmog@microsoft.com>
Cc: Vincent Hardy <vhardy@adobe.com>, W3C style mailing list <www-style@w3.org>
On Thu, Jun 2, 2011 at 2:59 PM, Alex Mogilevsky <alexmog@microsoft.com>wrote:

>  I fully agree it is important to have a precise page breaking spec. I
> don’t see however why regions progress has to be blocked by it. As of today,
> page breaking behavior is very underspecified, pretty much any non-trivial
> issue produces 12 different results in 4 major browsers.

We've gotten away with it so far because containers with varying width don't
come up all that often --- currently only when printing and authors use
@page rules to change the available width on particular pages, and there's
not a lot of need for that.

But with regions, we will have variable-width containers almost any time
regions are used.

 CSS Regions spec defines how to describe a set of containers for content to
> flow through. That definition can be solid without any new details on how
> content is broken between pages. It can even apply to non-css content (why
> not SVG? Or PDF?).

I'm not saying it has to be in the Regions spec. It would make sense for the
changes to be in their own spec or distributed across other CSS3 modules
that update the spec of block-and-line etc.

I'm saying that if we start shipping implementations of Regions without a
spec for how variable-width containers work, we will have a big problem.

"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
Received on Thursday, 2 June 2011 03:38:41 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:46 UTC