W3C home > Mailing lists > Public > www-svg@w3.org > May 2011

Re: [SVGIntegration] Too many referencing modes

From: Doug Schepers <schepers@w3.org>
Date: Fri, 13 May 2011 00:26:24 -0400
Message-ID: <4DCCB2F0.8070708@w3.org>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: www-svg <www-svg@w3.org>, Boris Zbarsky <bzbarsky@MIT.EDU>
Hi, folks-

Tab Atkins Jr. wrote (on 5/12/11 8:56 PM):
> It appears that too many referencing modes are defined in the SVG
> Integration draft
> <http://dev.w3.org/SVG/modules/integration/SVGIntegration.html>.  In
> practice, it appears that all we require is "Dynamic Interactive" and
> "Secure Animated" mode.  At least within HTML/CSS, "Dynamic
> Interactive" covers the behavior when SVG is embedded via<iframe>,
> <object>, or<embed>, while "Secure Animated" covers the behavior when
> it's embedded via<img>  or as a CSS image.
> Are there known contexts where any of the other modes are actually necessary?

SVG Integration is not only for the common HTML+CSS case, but for a wide 
variety of use cases.  We've heard similar feedback in the past about 
too many referencing modes, and each time, talking through it, we've 
come up with real-world scenarios where each is useful.  I have an 
action to add such example use cases to the spec for each referencing mode.

SVG is used beyond the Web, in office formats, secure scriptless 
environments for technical schematics, as an icon or symbol format, and 
lots of other places.  The aim of this document is to make it easier for 
people working on these specs to think about the different constraints 
and to guide them to make intelligent choices about how best to 
integrate SVG for their use case.

Boris Zbarsky wrote (on 5/12/11 9:14 PM):
>  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?

> 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, but I don't have 
strong feelings about it myself.  This is still an editor's draft, so 
I'm open to suggestions.

At the Auckland F2F, we discussed some other important considerations 
(perhaps more important than the ones I've laid out), so I plan to 
change the spec based on that discussion.

-Doug Schepers
W3C Team Contact, SVG, WebApps, and Web Events WGs
Received on Friday, 13 May 2011 04:26:26 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:25 UTC