Compiler switch to build a custom-element-only web component

[dschulten]

Svelte Webcomponents fail in IE11 both with the official webcomponents-loader polyfill and the shadow-dom polyfill by @tuespetre.

Shadow DOM is not considered production ready by many, as opposed to custom-element.

For the acceptance of Svelte webcomponents it would be useful if we were able to build them as pure custom-elements without shadow dom.

[tuespetre]

@dschulten would you be able to point me to a demo of the problem? Solid IE11 support was a big sticking point for us so Inwoild be happy to take a look.

[dschulten]

for issues with IE11 support using the shadow-dom polyfill, see tuespetre/shadow-dom#7 and #1171

[dschulten]

It might be easier to fix #1171, and in that case #1171 is more important for me.
I still think it would be useful to build custom-element webcomponents without shadow-dom, e.g. there are situations where you might not want to isolate the CSS but really use the site style, e.g. for a pattern library on a corporate website. See Rob Dodson's The case for custom-elements

[patrickalima98]

I agree with @dschulten, this is very important to develop projects with Svelte, I think this should be a high priority feature, in my case, we are building a library of components like UI Fabric from Microsoft, but we can not move forward because of the Shadow Dow, this prevents styling the buttons inside cards and other complex structures.

Not only for this reason but also for all other reasons already listed in this and other issues, it would be very good if this problem could be solved.

[Conduitry]

This is the older issue, but #1748 is more thumbed-up and seems to have more relevant information and discussion than this one, so closing this.