To accompany contemporaneous discussions establishing levels of support for SVG in various browsers, I would like to clarify a sub-point.
What methods (perhaps even reliable methods) are favoured for on-the-fly 'detecting' support of SVG either in part or whole? By 'whole' I mean detection of outright capability to accept SVG - does it: accept SVG and have a go at rendering (perhaps missing out animation, effects, xlinking to events, etc); accept SVG but do nothing useful; not accept SVG and complain overtly or offer to download the document instead? By 'in part' I imply within the first two options above: can we usefully or reliably test on an individual 'element' basis whether we're going to get expected results or not, for such things as smil anim, effects, xlink, and so on. I mention this in a similar vein to how javascript practitioners, after the first browser war, adopted a stance of live testing almost each keyword for its existence, before executing it. Can we do this in SVG? A live test rig (perhaps as a prolog part of each svg doc) that affords granular degradation (and perhaps svg frameworks). [Non-text portions of this message have been removed] ------------------------------------ ----- To unsubscribe send a message to: [EMAIL PROTECTED] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ----Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/svg-developers/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
