- From: Kevin Schaaf <notifications@github.com>
- Date: Wed, 07 Mar 2018 05:35:59 +0000 (UTC)
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 7 March 2018 05:36:57 UTC
I think what we'd actually like is to open discussion about the potential for an `SVGTemplateElement` to be added to the platform (with otherwise identical behavior to `HTMLTemplateElement`, consuming its SVG-namespaced child elements into its `.content` fragment), or some other means of getting equivalent functionality. It seems like a hole that we have a platform primitive for parsing and then efficiently cloning copies of inert HTML but not SVG; and more-so that we're considering adding more functionality to `<template>` ala TemplateInstantiation which would currently exclude SVG use cases (despite the fact that a developer needing to repeat a list of svg fragments from a template is arguably no stranger than needing to repeat a list of divs). Is that still a `whatwg/html` concern, or does it belong here? Also, was template support in SVG litigated in the original `<template>` discussions and rejected or deferred for some reason? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/744#issuecomment-371028483
Received on Wednesday, 7 March 2018 05:36:57 UTC