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

Robert, I am not trying to be defensive (I don’t take technical issues personally, or I won’t be doing this), or reckless (I have implemented things before that were not backed up by good specs… heard about “zoom” property?).

Let’s together figure out the best way to approach this. Can we start a list somewhere of what a good pagination/fragmentation spec needs to have? Once we have it we can decide which spec it belongs to.

From: [] On Behalf Of Robert O'Callahan
Sent: Thursday, June 02, 2011 1:54 PM
To: Alex Mogilevsky
Cc: Vincent Hardy; W3C style mailing list
Subject: Re: [css3-regions] New CSS Regions editor draft

On Thu, Jun 2, 2011 at 4:23 PM, Alex Mogilevsky <<>> wrote:
We are going to have variable-width regions, and it will be common. What aspects of content pagination we need to have clarified or defined in order to be able to have interoperable implementations of a usable set of important use cases?

That bar is too low. If we have interop on a usable set of important use cases, but no interop on a large set other important use cases, we will have created a large problem for Web authors.

I hope that the days are behind us when we could just bang out a feature that works in some common cases and leave a lot of its behavior undefined.
 Once we come up with a list that needs to be resolved, we can decide what spec it should be in. I personally don’t see any problem implementing CSS3 Regions and CSS4 Paged Media together if it is what it takes to render content that we all care about.

I don't, as an implementor, but it seems weird for a CSS3 spec to only make sense if you implement a CSS4 spec as well ... just from a version numbering point of view.

"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 06:51:19 UTC