I feel pretty strongly that the SVG behavior is not appropriate. I think any sort of invalid 'filter' value, including a <filter> element with a child element of unknown type, should cause the filtered element to be rendered normally (i.e. 'filter' treated as 'none'). Otherwise I think introducing new <fe> SVG element types does not get useful fallback. Regarding Dirk's question, I don't think it matters much but I lean slightly towards option 1. It's probably better to not apply a filter at all than apply a possibly mangled filter. Rob -- Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, 'm aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp waanndt wyeonut thoo mken.o w * *
Received on Friday, 12 July 2013 21:25:38 UTC