RE: [css3-exclusions] ordering exclusions by z-order

> -----Original Message-----
> From: rocallahan@gmail.com [mailto:rocallahan@gmail.com] On Behalf Of
> Robert O'Callahan
> Sent: Monday, May 21, 2012 5:48 PM
> 
>> On Sat, May 19, 2012 at 5:25 PM, Rossen Atanassov
>> <Rossen.Atanassov@microsoft.com> wrote:
>> Every element can generate multiple boxes due to fragmentation and exclusion
>> elements are no exception. This is why we try to be consistent in the spec and
>> talk in terms of exclusion boxes and not elements.
> 
> The spec does mention "exclusion elements" quite a bit, and in some places the
> text assumes that there is one exclusion area or shape per element.

The spec does mention 'element' in quite a few places when we refer to element related topics such as property applicability etc. We only refer to 'exclusion elements' in the places we define it and the properties applicable to them. I can't deduce any assumptions about shapes or multiplicity being a problem from the current text. Perhaps I'm missing it?

> Perhaps you can eliminate any mention of "exclusion box" and "exclusion area"
> and simply talk about "exclusion elements" and their "exclusion shapes" where
> an element can have more than one exclusion shape associated with it. Having
> exclusion elements, shapes, boxes and areas is too much!

The concepts defined in the spec are intended to be pretty clear and we try to use them very systematically when talking about content related topics such as property applicability, inheritance etc. (elements or exclusions elements) and layout (exclusion boxes, areas and contexts). As to shapes, we wanted to have these in a separate section in case the spec splits in two - exclusions and shapes. These are currently related features but they are definitely separable and we don't want to mix them.

Thanks,
Rossen

Received on Thursday, 31 May 2012 01:40:53 UTC