W3C home > Mailing lists > Public > www-style@w3.org > September 2000

Re: Problems understanding positioning

From: Stephanos Piperoglou <stephanos@webreference.com>
Date: Mon, 18 Sep 2000 23:59:34 +0100 (BST)
To: Maury Markowitz <maury@sympatico.ca>
cc: www-style@w3.org
Message-ID: <Pine.LNX.4.21.0009182355010.12941-100000@highnoon.spn>
On Thu, 31 Aug 2000, Maury Markowitz wrote:

>   Why does the position depend on a specifically positioned element.
> Why isn't it _always_ it's parent element?

Basically, because this allows you some control over which element you
want to position relative to, while otherwise you'd be stuck with the
parent. Of course, what would be really nice would be (somebody
mentioned this recently):

postition: relativeto('reference');

Where the element is positioned relative to the containing block
defined by the content area of the element with ID "reference".

This is wishful thinking, though. As you pointed out, IE5.5/Win does
such a lousy job with positioning this is the last thing you're
worried about (IE4 and IE5 did similar things; it seems that IE will
randomly collapse margins and paddings with each other, and this
usually depends on what unit they're specified in. Go figure).

-- 
Stephanos Piperoglou                              <stephanos@webreference.com>
Maintainer, HTML with Style                    <http://webreference.com/html/>
  Visit HTML with Style for online HTML and CSS tutorials with step-by-step
   procedures and practical examples to help you author Web pages that are
 full-featured, standards-compliant and backwards-compatible, tools to make a
 Web author's life easier, software reviews, opinions, industry news and more
Received on Monday, 18 September 2000 16:58:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:05 GMT