W3C home > Mailing lists > Public > www-style@w3.org > July 2005

Re: New layout language.

From: <Kris@meridian-ds.com>
Date: Wed, 6 Jul 2005 09:15:21 -0500
To: www-style@w3.org
Message-ID: <OFCF702BC0.0AEDF3B7-ON86257036.004E4F27-86257036.004E4F76@meridian-ds.com>

Laurens Holst Wrote:

>Kris@meridian-ds.com wrote:
>Kris, why use margin at all? Margin is for margins. Not for positioning.

Well my whole point in minimum margins is this:

Sometimes I'm going to use a % margin, and if, I have two % margins moving
against each other (IE margin-left:50% and margin-right:50%) on two
elements sitting next to each other, with min-widths, at some point in an
absolutely positioned system, these two objects will intersect.

No, I'll be the first to mention that in my layout to Orion (which is where
I ran into the issue) I used things like "left:50%; margin-left:5px; to get
the spacing I needed, however, that doesn't mean that it couldn't be
userful, and more accurately, perhaps a min-left: attribute would be more
useful still.  If we're going to specify minimum widths and heights for
elements then we obviously have some sort of minimum static appearance we'd
like to maintain.  Currently I know of no way to do such a thing with the
spacing between objects.  While I've not run into this problem with
relative and static positioning, absolute can be a pain in this reguard due
to the fact that each object is absolutely placed in space, and a
percentage based absolute system with min-width/heights specified, will
eventually fail at some resolution.

That make sense?  or does the mechanism exist and I'm just ignorant?

Received on Wednesday, 6 July 2005 14:15:48 UTC

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