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

Re: [CSS21] Issue 195 - relative positioning of inlines containing blocks - comments on Working Draft

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 10 Jan 2011 13:57:21 -0800
Message-ID: <AANLkTikcLL0Uf7w9beh28hmYb0rDm2cen97p7aQtw6ma@mail.gmail.com>
To: Anton Prowse <prowse@moonhenge.net>
Cc: "www-style@w3.org" <www-style@w3.org>
On Fri, Jan 7, 2011 at 1:09 PM, Anton Prowse <prowse@moonhenge.net> wrote:
> As a result of the resolution of Issue 195,[1] (Anonymous block
> boxes) now says:
>  # When an inline box contains an in-flow block-level box, the inline
>  # box (and its inline ancestors within the same line box) are broken
>  # around the block-level box, dividing the inline box into two pieces
>  # even if either side is empty. [...]. When such an inline box is
>  # affected by relative positioning, the relative positioning also
>  # affects the block-level box contained in the inline box.
> What does "affects" mean here?  That the block-level box behaves as if it
> itself has position:relative?  Or merely that its location on the canvas is
> translated along with that of the inline?
> The difference is important because in the former case the z-index stacking
> could be affected.  I suggest we use a clearer wording here.
> [1] http://wiki.csswg.org/spec/css2.1#issue-195

The latter.  I agree that some slightly clearer wording is warranted.

Received on Monday, 10 January 2011 21:58:14 UTC

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