TRACK.md

Track

Svelte animations not working with custom elements (aka web components)

• Transitions on WebComponents not working
  • closed, because of being duplicate, but has workarounds
• Transitions in custom Elements
  • with proposed PR

Svelte: setting props of web components

Note: No longer essential for us. Track anyhow, for general interest.

• Prop initialization in web/standalone components

  This is more severe than it looks. And it looks severe...

  In our case, passing a prop to a web-component-within-web-component seems fully impossible. Strange.

  • PR #5139

Svelte: web components readiness (aka 'custom elements')

• issues with feature: custom element

  • 21-Feb-21: 39 open 👍
  • 17-Jan-21: 41 open

Svelte: ability to have normal (private) components, used by a web component

• Feature: allow components to opt out of custom elements build

  Would welcome it, though the work-around we have (two svelte steps in the Rollup config) works great!

Svelte: CSS within custom element (sub-elements) is lost

Haven't found an issue for this. #help: Report to Svelte?

See GoogleProvider.svelte. It has a style section that is completely ignored in the process.

(Did not start seeing the generated code to understand where it gets lost. But in order for Svelte to be powerful in making (also) web components, such an elementary abstraction should just work.