Re: [SVGIntegration] Too many referencing modes

Hi, Boris-

Boris Zbarsky wrote (on 5/13/11 1:13 AM):
> On 5/13/11 12:26 AM, Doug Schepers wrote:
>>> From Gecko's perspective, "Animated Mode" is NOT acceptable for
>>> <html:img>, and not acceptable for <svg:image> for the same reasons.
>>
>> I've heard differently from other browser vendors. What's your rationale?
>
> See https://bugzilla.mozilla.org/show_bug.cgi?id=628747
>
> If other browser vendors choose to expose their users to that sort of
> privacy leak, I guess that's up to them. But the spec shouldn't
> recommend using this mode for things like <html:img> without
> highlighting the possible issues that result.
>
> Did this never get brought up on this list? The plan was to bring it up
> here...

It doesn't ring a bell, but I might be forgetting it.  External 
same-domain references should be okay, though, right?


>>> We also have no plans to do different things for <img> and background
>>> images (hence there is no point in "Static Mode" from our point of view;
>>> it's not like we prevent animated GIFs or APNG in CSS backgrounds, so
>>> why would we prohibit declarative animation of SVG?).
>>
>> Okay. Again, others have been of a different opinion
>
> OK. Again, I have no problem with the mode existing so much (I can
> always just ignore its existence as an implementor); I have problems
> with the spec recommending, for reasons that are unclear to me, that
> animated SVG not be supported in CSS background images.

Fair enough.  The rationale was that people were concerned about the 
possible performance issues, especially for tiled declarative 
animations.  If that's not a real problem

Note that this spec is still just an editor's draft, and has not yet 
been published as a First Public Working Draft, so you should expect it 
to be a bit rough in places; feedback is welcome to improve it before 
it's ready for FPWD.

Regards-
-Doug Schepers
W3C Team Contact, SVG, WebApps, and Web Events WGs

Received on Friday, 13 May 2011 05:41:35 UTC