Bill Brown wrote: > > Turns out, it's a half fix. It DOES draw significant resources on very long > pages. I've changed the * selector to a class (minMax) and applied the class > to > five elements, much like one applies a clearFix. I noticed a nearly neglible > delay when I applied the class to more than five elements. Assuming that gets > amplified by factors like pc speed, connection and so on, five seemed safe. > > New Page: http://macnimble.com/sandbox/ieMinMax2.html > > Is that faster Ingo?
Thanks. Yes, this is much faster. Although fast selecting cross the lines still is delayed, but barely noticeable here. Other testers will test this with other configurations. I think this method could become very useful. What's mostly intriguing to me about this is that IE > expressions are able to find the incorrectly named minWidth, maxWidth and > maxHeight styles, presumably from the DOM? Even more fascinating is that it IS > able to locate the min-height style using correct syntax. I don't know if this is correct or incorrect. Ingo -- http://www.satzansatz.de/css.html ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
