- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Jun 2017 03:34:06 +0000
- To: public-svg-issues@w3.org
Ah, thanks @tshinnic. I should have thought to check different types of elements. (And thanks for your effort trying to make sense of the path grammar, too! For exponential numbers: not a lot in web design, but some SVG WG members were working on converting technical drawings to SVG, and those sometimes use very different scales. But getting browser to render them reliably has been a problem.) Regarding overflow: Markers are _never_ expected to have a scroll bar, so that was why the spec says `auto` should always be treated as `visible`. And that [was in SVG 1.1](https://www.w3.org/TR/SVG11/masking.html#OverflowProperty): "Within SVG content, the value auto is equivalent to the value visible." The decision on SVG 2 was to confirm that rule, and also add guidance for inline `<svg>` elements in CSS/HTML contexts. For inline `<svg>`, SVG 2 says that `auto` should be _either_ `visible` or `scroll`. But none of the browsers currently add scroll or pan widgets to `<svg>` other than the root element of a browser tab or iframe. (And some browsers don't even do it for iframe.) -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/329#issuecomment-311853329 using your GitHub account
Received on Thursday, 29 June 2017 03:34:14 UTC