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

Re: [css-regions] Comments

From: David Hyatt <hyatt@apple.com>
Date: Fri, 11 Mar 2011 12:49:37 -0600
Cc: "robert@ocallahan.org" <robert@ocallahan.org>, Jacob Refstrup <jrefstrup@apple.com>, "www-style@w3.org" <www-style@w3.org>, "agourdol@adobe.com" <agourdol@adobe.com>
Message-id: <DADF071F-8DD6-4059-AC89-B1D11901BADD@apple.com>
To: Brad Kemper <brad.kemper@gmail.com>
On Mar 10, 2011, at 8:15 PM, Brad Kemper wrote:

>> There are two features that we wanted to support here.  The first is the ability to choke the propagation of the exterior wrap paths outwards.
> Do you mean that there would be some distance between the path/alpha edge and items that wrap around it? Could we use 'margin' for that (a margin that followed the path)? Or are you talking about something else?

No, I'm talking about the fact that sometimes you want wraps to propagate and sometimes you don't.  For example you might want to create a group of images and have all of their wraps affect the surrounding content even if those images are inside a container that was used to position them.  For example imagine a stack of centered images in a page inside a single positioned container used to do the centering, and you want the text to avoid all of them.  There are times where you won't want the wraps to propagate through containers, i.e., you just wanted the wraps to affect your own textual content.  This may be the case with separate text sections (like asides).  I think a rule of not propagating if you have any normal flow content might be sufficient for this though.

As for margin inflating the path, yes, we had that idea also.  Since the notion of box side gets kind of silly when you are considering an irregular shape, you'd probably just use the max of all the margin side values to inflate.

Received on Friday, 11 March 2011 18:50:11 UTC

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