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

RE: [CSS21] 10.1: Issues with "containing block"

From: John Jansen <John.Jansen@microsoft.com>
Date: Tue, 15 Mar 2011 16:40:51 +0000
To: Peter Moulder <peter.moulder@monash.edu>, www-style list <www-style@w3.org>
Message-ID: <C340671BECD4364E8F9EBA27E8E231322DF90E51@DF-M14-04.exchange.corp.microsoft.com>
Hello Peter,

The CSSWG resolved to  make this undefined in the CS2.1 specification [1] as per the edits to issue #215, which makes it undefined what containing block is formed by a relpos inline that splits across multiple lines.

We hope this closes your issue.

Please respond before 18 March, 2011 if you do not accept the current resolution.

[1] http://w3.org/TR/CSS

> -----Original Message-----
> From: www-style-request@w3.org [mailto:www-style-request@w3.org] On
> Behalf Of Peter Moulder
> Sent: Sunday, November 28, 2010 10:53 PM
> To: www-style list
> Subject: Re: [CSS21] 10.1: Issues with "containing block"
> 
> On Sat, Oct 23, 2010 at 07:13:55AM +1100, Peter Moulder wrote:
> 
> >     So one test case would involve a position:absolute element with a
> >     display:block parent that in turn has a display:inline position:relative
> >     parent.
> 
> The result of that test is that the containing block for Gecko is based on the
> display:inline position:relative element that was split (so is apparently based
> on element tree), while in Konqueror/WebKit/Chromium, the containing
> block in the test was the initial containing block, presumably indicating that
> it's going by box tree ancestry.
> 
> I noted previously that the editors' draft made the change
> 
>   "[If] the ancestor is inline-level"
>  ->
>   "[If] the ancestor is an inline box",
> 
> though note that the editors' draft is still written in terms of an element, i.e.
> the new text might more completely be written as:
> 
>   "[If] the ancestor [of the element] is an inline box"
> 
> so it's still rather unclear as to whether the spec is asking for box tree
> ancestry or element tree ancestry, i.e. it's still unclear whether Gecko or
> Konqueror and its descendants have the "right" behaviour.
> 
> Obviously this an implementability issue for CSS2.1: one cannot implement
> section 10.1 without knowing what the containing block for the
> position:absolute element is, and hence what its left coordinate is.
> 
> pjrm.
> 
> 
> <html>
> <head>
> <title>Test of position:absolute containing block when closest element
> differs from closest box</title> </head> <body> <p>Here is a paragraph
> containing a <span style="position:relative;">position:relative span that is
> split by a <span style="display:block">block-level element that contains a
> <span style="left:0; position:absolute; background-
> color:cyan;">position:absolute span</span> ... <br /> in the middle of
> it</span> before this remainder of the position:relative span</span> and
> the rest of the paragraph.</p> </body> </html>
> 
Received on Tuesday, 15 March 2011 16:41:26 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:38 GMT