On 4/11/2014 4:38 am, Paul LeBeau wrote: The Error Processing section of the SVG spec says: "The document shall be rendered up to, but not including, the first element which has an error."
Would not a bad input, such as a bad URL reference be counted as an error? If so, processing should(?) stop at the filter primitive before the <feImage>. Which to me sounds exactly like option 3. It's a bit different than option 3, because that error processing text says to stop rendering the entire document from that point onwards (probably from the element being filtered rather than the filter element itself). Option 3 only affects the result of the element being filtered, it doesn't halt rendering of the rest of the document. I think the above text is more relevant to syntax errors than missing resources. Option 2 is nice in terms of helping an author diagnose the problem but can be equally well achieved with a console message. Option 1 seems most permissive in terms of allowing an author to specify an invalid resource with minimal impact on the rest of the filter - would anyone ever want to do that? Nikos The information contained in this email message and any attachments may be confidential and may also be the subject to legal professional privilege. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. If you have received this email in error, please immediately advise the sender by return email and delete the information from your system.
