Re: Handling of <view> element

As you suggested, I have created a bug.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22457

Paul




On 26 June 2013 02:02, Robert Longson <longsonr@gmail.com> wrote:

> Paul,
>
> That was the wrong bit of the overflow text. As this is the outermost or
> root element we clip per this bit...
>
>    - When an outermost svg element<http://www.w3.org/TR/SVG/intro.html#TermOutermostSVGElement>is stand-alone or embedded inline within a parent XML grammar which does
>    not use CSS layout or XSL formatting, the ‘overflow’<http://www.w3.org/TR/SVG/masking.html#OverflowProperty>property on the outermost
>    svg element<http://www.w3.org/TR/SVG/intro.html#TermOutermostSVGElement>is ignored for the purposes of visual rendering and the initial clipping
>    path is set to the bounds of the initial viewport<http://www.w3.org/TR/SVG/coords.html#SVGViewport>
>    .
>
> As to the "*If the SVG fragment identifier addresses a ‘view’ element
> within an SVG document then the closest ancestor ‘svg’ element is displayed
> in the viewport*" I didn't understand it either so I ignored it when I
> implemented it ;-) Raise a bug in bugzilla if you want and if we can agree
> on something that makes sense that is in accord with other UAs I'll think
> about implementing it if I can understand what to do.
>
> Robert.
>
>