Digression: On Tuesday, 6 November 2012, Susanne Jäger wrote: > > But all other methods have a real effect (and side effects), that may not > fit in a special environment. zoom: 1; is wonderful meaningless, it does > nothing (beside fixing a stupid old IE bug). The only real problem I see, > is that you might miss an important validation error, when you get used to > ignoring some. >
Actually, IE's zoom property has some wonderfully useful effects other browsers take a lot of hacking to reproduce — the ever-popular clearFix among them. More on the subject here: http://www.stubbornella.org/content/2010/12/09/the-hacktastic-zoom-fix/ Its meaning is pretty clear (although that's not what it's used for here): apply a scalar zoom to the rendered element (with a value of 1, of course, there's little appreciable effect). As I mentioned earlier, this is now implemented by WebKit too. Coincidental that zoom was among many advanced graphical layout properties shipped with IE6's engine that other browsers are just starting to implement: transformation matrices are another extension in this direction. IE can be infuriating, but understanding it and working with it can be quite rewarding. Better the devil you know, in any case — at the moment I'm wrestling with buggy Android WebKit box model issues relating to transform, and it's not pretty — neither is it documented. Here again, W3C validity is little comfort. -- Regards, Barney Carroll [email protected] +44 7429 177278 barneycarroll.com ______________________________________________________________________ css-discuss [[email protected]] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
