W3C home > Mailing lists > Public > www-svg@w3.org > April 2010

Re: SVGZoom

From: Francis Hemsher <fhemsher@gmail.com>
Date: Wed, 7 Apr 2010 03:49:03 -0300
Message-ID: <n2gc41bcc9d1004062349s61fdf04p99370c2563271889@mail.gmail.com>
To: Patrick Dengler <patd@microsoft.com>
Cc: www-svg@w3.org
Hi Patrick,

Along the same line...I'm hoping SVGZoom would also apply to inline SVG.
If not, then the user would be confused if they were expecting
Zoom/Pan of an SVG image located in the HTML container file: The user
isn't aware if the SVG image is in an iframe, object, image, embed, or
inline. Therefore, inline SVG should employ SVGZoom (an viewBox) in
the same manner as if it were a .svg file(SVG Document).

Regards,
Francis

On 4/2/10, Patrick Dengler <patd@microsoft.com> wrote:
> SVGZoom is only supposed to fire on the "outermost svg element" which is
> defined as "outermost svg element: The furthest 'svg' ancestor element that
> remains in the current SVG "document fragment". So the "outermost svg
> element" is any svg element that is at the top of a "document fragment".
>
> And
>
> "When an 'svg' element is a descendant of another 'svg' element, there are
> two SVG document fragments, one for each 'svg' element. (One SVG document
> fragment is contained within another SVG document fragment.)"
>
> So every 'svg' element is an "outermost svg element" because every 'svg'
> element is the root of a document fragment.
>
> Which means that SVGZoom should fire on every 'svg' element.
>
> This doesn't seem right to us.
>
> Thoughts?
>
>
Received on Wednesday, 7 April 2010 06:49:35 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:44 GMT