On 7/12/13 5:25 PM, Robert O'Callahan wrote: > 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. OK, should that be raised as an issue on SVG, then? I feel like we should have consistency between the case when there is only one url() in 'filter' and the case when there are multiple things including a url()... -BorisReceived on Friday, 12 July 2013 21:31:31 UTC
This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:32 UTC