Could we please raise the priority of this issue? IMHO this issue is an absolute show-stopper for the adoption of webcomponents. E.g.: We had to refactor our application that was using Polymer to basically get rid of all web components that used SVG. We had to pull those components to the document top-level and make them plain HTML instead of web components to make the application work in Safari. This worked for some components but was not feasible for others, where the functionality is still broken, now. With the webcomponents shims the situation was actually better for us, but now that Safari has an implementation which does not allow using SVG with `use` elements the only workaround for devs is to drop web components. Also I fear that our applications (which work great in Chrome right now) might cease to work in Chrome, too, once they decide to "stick to the spec" and cripple the (now working) SVG functionality in Chrome, too. -- 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/179#issuecomment-328784474
Received on Tuesday, 12 September 2017 08:41:27 UTC