- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Aug 2016 21:28:21 +0000
- To: public-svg-issues@w3.org
Not an accident, part of the shadow DOM re-write. A `<use>` element is now treated more like a container than a graphics element. Specifically, it does not render any content to screen directly, the visible content is rendered by the individual elements in the shadow DOM. (Note, `<use>` still inherits from SVGGraphicsElement interface, but so do other graphical container elements like `<svg>` and `<g>`, which aren't included in the "graphics element" definition.) Was there a specific place where this change has thrown off the content model of another element? I thought I'd checked & it was always covered by another category, but I may have overlooked something. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/229#issuecomment-237049949 using your GitHub account
Received on Tuesday, 2 August 2016 21:30:30 UTC