Re: [css3-values] dropping min()/max() on calc()

• From: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
• Date: Thu, 09 Sep 2010 08:08:03 +0200
• To: "L. David Baron" <dbaron@dbaron.org>
• Cc: www-style@w3.org
• Message-ID: <4C8879C3.1040202@disruptive-innovations.com>

Le 08/09/10 22:39, L. David Baron a écrit :

> I'm leaning towards dropping min() and max() support from the calc()
> implementation in Mozilla.
>
> They make a whole bunch of things a good bit more complicated,
> nearly impossible, or actually impossible, such as determining if
> there is a percentage basis that could make an expression nonzero,
> or computing certain cases of intrinsic widths correctly.
>
> Are there any strong reasons for keeping min() and max()?  (I think
> I was one of the original advocates of adding them.)
>
> -David
>

Seen from here, and after direct chats with lots of web designers,
calc() is the most important thing, something that will DRASTICALLY
change their daily work if interoperably implemented.
min() and max() are far less important.

I say let's start with calc() only, that's already a lot.

</Daniel>

Received on Thursday, 9 September 2010 06:08:34 UTC