W3C home > Mailing lists > Public > www-style@w3.org > June 2008

Re: [CSS 2.1] static position of an absolutely positioned element with auto-offsets

From: fantasai <fantasai.lists@inkedblade.net>
Date: Tue, 10 Jun 2008 20:29:20 -0700
Message-ID: <484F4690.7050005@inkedblade.net>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: "www-style@w3.org" <www-style@W3.ORG>

Boris Zbarsky wrote:
> fantasai wrote:
>> My take from that bug is that both 'position' and 'float' are ignored
>> (set to 'static' and 'none' respectively) when finding the static 
>> position.
>> Is that correct?
> In Gecko, yes.  Other UAs' behavior seems to match that.

So if that's true and the hypothetical position is calculated after first
recomputing 'display' with those assumed values, the following edits:

   # if its 'position' property had been 'static' and 'float' had been 'none'
   | if its specified 'position' value had been 'static' and its specified
   | 'float' had been 'none'
in both
   10.3.7 - http://www.w3.org/TR/CSS21/visudet.html#abs-non-replaced-width
   10.6.4 - http://www.w3.org/TR/CSS21/visudet.html#abs-non-replaced-height

should clarify this since replacing values at the specified value stage
would require recomputation of 'display'. It also avoids saying anything
about reading the specified value of 'display' and so avoids any issues
with 'initial' or 'inherit' keywords.

Does that look correct or am I missing something?

Received on Wednesday, 11 June 2008 03:29:56 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:37 UTC