>
> Bill, I am clueless when it comes to scripting.
>
> * {
> height: expression( ... ? ... :auto);
> ...
>
> wouldn't that let the costs of this function get too height
> in longer documents with many elements, as every element has
> to be parsed?
>
> I have inserted your set of expressions in a long document
> (the onhavinglayout one, in the head section of the file,
> without declaring any minHeight).
>
> My standalone IE6 at least lost any performance in scrolling
> and resizing. Selecting a paragraph was delayed to 4 seconds.
>
> Maybe I did something wrong.
>
> Ingo
Aha! Excellent point, Ingo. See...I knew I joined this list for a reason.
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? 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.
___________________________________________________________
$0 Web Hosting with up to 200MB web space, 1000 MB Transfer
10 Personalized POP and Web E-mail Accounts, and much more.
Signup at www.doteasy.com
______________________________________________________________________
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/
