- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Jul 2016 16:38:50 +0000
- To: public-svg-issues@w3.org
Re `foreignObject` and width/height: > Is this just about what's useful to authors? It sounds like we should use width and height on the use. It's more about what is consistent / clear. An `<image>` doesn't adjust its size based on the `<use>` width & height. Neither does a `<rect>`. Since a `<foreignObject>` doesn't take a `viewBox` attribute, I'm leaning towards not including it in the size-to-fit effect. If & when we re-define `viewBox` as a presentation attribute that can apply on any element, then we can change the `<use>` behavior to kick in whenever a new viewport is created in the child content. So the change is really a matter of cleaning up the section on viewport-creating elements to distinguish between the different cases. A `<foreignObject>` doesn't create a new SVG coordinate system, anyway: it creates a new CSS box model container. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/pull/206#issuecomment-234006448 using your GitHub account
Received on Wednesday, 20 July 2016 16:39:01 UTC