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

Re: [box-sizing] and min/max/width/height was Re: [css3-ui] editor's draft updated per [CSSWG] Minutes and Resolutions F2F Kyoto Sat: CSS3 Fonts, Regions, @viewport, Variables, @supports, Selectors4, Administrivia

From: Tantek Çelik <tantek@cs.stanford.edu>
Date: Thu, 14 Jul 2011 10:57:06 -0700
Message-ID: <CAOACb=+kD1CAjqsTRYDPLophX3mZKRUyNS3JQCMH-ZQp26WRjA@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: www-style@w3.org
On Thu, Jul 14, 2011 at 10:48, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 7/14/11 1:36 PM, Tantek Çelik wrote:
>> Bug filed here on Firefox:
>> https://bugzilla.mozilla.org/show_bug.cgi?id=308801
>> feel free to add your supportive statements for fixing min-/max-
>> width/height with box-sizing.
> Does something actually define how this stuff is supposed to interact with
> the replaced element stuff at
> http://www.w3.org/TR/CSS21/visudet.html#min-max-widths (sadly no way to link
> directly to that algorithm)?  Last I checked this algorithm didn't make much
> sense for non-content-box values of box-sizing if those affected how
> max/min-width/height work.
> An actual spec for how this is supposed to work for replaced elements is the
> primary blocker for work on the above linked bug, and has been for years.
>  And I've said so several times (to no effect so far, as far as I can see).

Do you have a test case posted demonstrating what you mean by "how
this is supposed to work for replaced elements"?



http://tantek.com/ - I made an HTML5 tutorial! http://tantek.com/html5
Received on Thursday, 14 July 2011 17:58:16 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:47 UTC