W3C home > Mailing lists > Public > www-style@w3.org > April 2009

RE: Control over collapsing margins

From: Niels Matthijs <niels.matthijs@internetarchitects.be>
Date: Wed, 29 Apr 2009 13:49:01 +0100
Message-ID: <EAD6F36F8B8A124FB32D722A828211FD088C8BA8@win-s-manc3.shared.ifeltd.com>
To: "Anton Prowse" <prowse@moonhenge.net>, <www-style@w3.org>

-----Original Message-----
From: www-style-request@w3.org [mailto:www-style-request@w3.org] On
Behalf Of Anton Prowse
Sent: 28 April 2009 23:33
To: www-style@w3.org
Cc: www-style@w3.org
Subject: Re: Control over collapsing margins

> This is certainly one use case, but I suspect there are other,
different
> ones.  Our task is to decide whether we only want suppression of
margin
> collapsing or whether we actually want BFC creation.  The trouble (in
> this particular case) with use-cases which are overly abstract and
> resemble minimal test-cases is that it's difficult to determine the
> practical difference between the two options.  I'd prefer to see full,
> real-world examples.

Hmmm, couldn't it just be seen from a more theoretical (but historically
proven) point of view?
I think it's obvious that the BFC property could be useful, but as an
only solution it will result in trouble. Maybe for now it's hard to find
real use cases, but we all know that before a property is implemented
and ready to use in css we are 3-4-5 years from now. Who knows what best
practises will be like then, and what problems we are likely to face.

Ruling out control over one effect (collapsing margins) and relying on 1
group of effects (BFC) sounds like a pretty bad plan to me. And it's not
because we can think of any reason why they shouldn't be grouped _now_
that it won't be an issue several years from now. There is no hurt in
having a property that just regulates collapsing margins I think. If
later you'd prefer an extra property that regulates the BFC of an
element that's fine too.

Just imagine a world where all graphical design elements are square.
Would you think it wise to create a property widthHeight and scratch
both separate width and height properties?

Greets,
Niels Matthijs
Internet Architects
Received on Wednesday, 29 April 2009 12:51:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 03:46:58 GMT