W3C home > Mailing lists > Public > public-fx@w3.org > October to December 2014

Re: [filter-effects] feImage with missing image resource

From: Rik Cabanier <cabanier@gmail.com>
Date: Mon, 3 Nov 2014 09:25:16 -0800
Message-ID: <CAGN7qDC4EZu5-ngZKzmyq0d_A03XAWcNOyeYwE1v493UhHDr9Q@mail.gmail.com>
To: Dirk Schulze <dschulze@adobe.com>
Cc: FX <public-fx@w3.org>
On Mon, Nov 3, 2014 at 6:14 AM, Dirk Schulze <dschulze@adobe.com> wrote:

> Hi,
>
> I checked the behavior of different SVG viewers on <feImage>[1] with a
> missing image resource. It appears that we have three behavior categories
> across 7 different SVG viewers (6 if you still count WebKit and Blink as
> one). Tested: Safari, Chrome, IE, Firefox, Opera (presto), Illustrator,
> InkScape (no result), Batik.
>
> All viewers apply an SVG filter on content even if <feImage> has a missing
> resource. Other then that, viewers either:
>
> 1) treat <feImage> as a transparent black image taking all primitive
> regions into account,
> 2) replace the missing image with a “missing image” icon and take all
> primitive regions into account or
> 3) treat <feImage> and all successor color manipulating primitives as null
> filter.
>
> Example: https://www.w3.org/Bugs/Public/attachment.cgi?id=1531
> Description: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27221#c0
>
> Option 1) looks reasonable for me and is easy to implement/specify. Option
> 2) looks strange but at least gives authors feedback of what is going on. I
> am unsure how to specify 3) and how it actually is implemented. Maybe
> someone from Mozilla could clarify.
>

I agree that 1) is the most reasonable option.
Can you break out which browser does what option?
Received on Monday, 3 November 2014 17:25:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:49:52 UTC