This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Created attachment 1531 [details] Example missing reference What happens if xlink:href of feImage references an invalid or not existing resource? The attached example has an feImage element that references a non-existent image. It is for testing purpose in different browsers. The test starts with inverting the SourceGraphic color so that we know if a filter was applied to the element or not. The it references the not existing image. The test also applies a subregion on the feImage element. Then the opacity of the feImage result gets inverted. Then we composite the previous result on top of the inverted SourceGraphic.
The result on various SVG viewers: Chrome: You see a "missing image" icon covering the top left quarter of an aqua colored square. Safari: You see a "missing image" icon covering the top left quarter of an aqua colored square. Firefox: You just see an aqua colored square. Opera (Presto): You see a black square covering the top left quarter of an aqua colored square. IE 11: You see a black square covering the top left quarter of an aqua colored square. InkScape: Crashes on windows. Batik: You see a "missing image" icon covering the top left quarter of an aqua colored square. Illustrator: You just see an aqua colored square. All viewers do apply the filter regardless of the missing image resource. But the behavior is pretty different across browsers. IE, Opera: Missing image is treated as transparent black. Firefox, Illustrator: Missing image acts as a null filter even for filter primitives applied on top of feImage. Safari, Chrome: General behavior as for IE, Opera but taking the "missing image" instead of transparent black.
Moved: https://github.com/w3c/fxtf-drafts/issues/193