- From: Sebastian Müller <notifications@github.com>
- Date: Tue, 15 Jan 2019 07:37:02 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 15 January 2019 15:37:24 UTC
To make this more search engine friendly and clear for the reader: * SVG won't work inside the shadow DOM if they contain local "use" elements * Shadow DOM breaks SVGs with "use" elements * You can either use Shadow DOM or use non-trivial SVG files, but both will not work * it feels like there is a bug and SVGs don't work as everyone (except the spec leads) would expect it, but this is actually by spec-design There is no efficient workaround or polyfill for this. The only options you are left with is to either ditch browser compatibility and hope that everybody uses a working version of Chrome or Firefox or shadow DOM, or SVG. Personal recommendation: Don't use Shadow DOM until this is fixed in the spec and in all browsers. Don't hold your breath, though; the original issue was opened almost four years ago and affects users in the real world for more than a year, now. Not using SVG or not supporting all major browsers is not a good alternative. -- 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/772#issuecomment-454436203
Received on Tuesday, 15 January 2019 15:37:24 UTC