Hi Garrett and other list members. Garrett Smith: > The better name would be something other than "filter" on a > CSSStyleDeclaration. Maybe "svgFilter".
Yes, that’s a possible solution to the issue, especially since it’s not particularly likely that many existing SVG documents use CSSStyleDeclaration to look up the 'filter' property at the moment. > > I don't think anybody is suggesting that these properties become part of the > > standard. It seems to me that a conforming implementation should be able to > > implement such compatibility hacks though, which is why they were brought > > up. > > Internet Explorer 4 had css filters that predates the SVG filter > (AFAIK). SVG filter creates a compatibility problem. Maciej says that > they worked around this by having style.filter return undefined, but > have that undefined be a special value that is == to "". I think it > would be a good idea to raise the issue with the SVG WG. If the SVG WG > wants to act in good faith, they should consider creating an > alternative property name for browsers, style.svgFilter, for example. I forwarded Maciej’s earlier mail to the SVG WG list for discussion: http://lists.w3.org/Archives/Public/public-svg-wg/2008OctDec/0377.html and an issue has been raised: http://lists.w3.org/Archives/Public/public-svg-wg/2008OctDec/0384.html -- Cameron McCormack ≝ http://mcc.id.au/ _______________________________________________ Es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
