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

I suspect that if there was a demand min-width and max-width, they
may be a particular solution for a more global problem, that min()
and max() could solve.

Let's see what other implementors are saying; if it's too complex
then we could live without it, but it could be a precious help in
some cases.

Regards,
François

-----Message d'origine----- 
From: L. David Baron
Sent: Wednesday, September 08, 2010 10:39 PM
To: www-style@w3.org
Subject: [css3-values] dropping min()/max() on calc()

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

-- 
L. David Baron                                 http://dbaron.org/
Mozilla Corporation                       http://www.mozilla.com/

Received on Wednesday, 8 September 2010 20:53:54 UTC