On Sun, 18 Jul 1999, Oren Ben-Kiki wrote: >> Unfortunately, to my knowledge noone has as yet worked out a suitable >> set of rules to make the cascade work well with !maximum and !minimum. >> (I do not know if anyone has even tried). > What is wrong with behaving as if each "attr: value" is a shorthand > for "attr: value ! minimum; attr: value ! maximum"? Cascading could > then be handled according to the current rules. Each property really needs three values; optimum, minimum and maximum (think of width, min-width and max-width). > I'd be more worried about clearly defining what algorithm the browser should > use to try to satisfy these constraints. It is this algorithm to which I was referring. -- Ian Hickson : Is your JavaScript ready for Nav5 and IE5? : Get the latest JavaScript client sniffer at : http://developer.netscape.com/docs/examples/javascript/browser_type.htmlReceived on Sunday, 18 July 1999 11:55:04 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:53:59 GMT