Another thought/question. Many versions of modern browsers support client-side XSL transformation, but as we all know no two XSL engines are created equal (especially when dealing with bloody IE ... but I digress).
To be honest, they're all quirky. Too qiurky for production use. In fact, I don't even use them for fun, because of the many quirks. What happens is that they work well at some high-level, but once you start looking at the details you see things that aren't working. Most of the time, something like a small CSS rule not matching, for no perceivable reason.
What you propose would be nice to have, but the conclusion these days would be "don't use client side XSLT" :-/
-- Robin Berjon <[EMAIL PROTECTED]> Research Engineer, Expway http://expway.fr/ 7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
