You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add ability to extend custom element class (#8991)
This should help everyone who has special needs and use cases around custom elements. Since Svelte components are wrapped and only run on connectedCallback, it makes sense to expose the custom element class for modification before that.
- fixes#8954 / closes#8955 - use extend to attach the function manually and save possible values to a prop
- closes#8473 / closes#4168 - use extend to set the proper static attribute and then call attachInternals in the constructor
- closes#8472 - use extend to attach anything custom you need
- closes#3091 - pass `this` to a prop of your choice and use it inside your component
- add some doc for #8987
Copy file name to clipboardExpand all lines: documentation/docs/04-compiler-and-api/04-custom-elements-api.md
+43-6
Original file line number
Diff line number
Diff line change
@@ -55,13 +55,28 @@ console.log(el.name);
55
55
el.name='everybody';
56
56
```
57
57
58
+
## Component lifecycle
59
+
60
+
Custom elements are created from Svelte components using a wrapper approach. This means the inner Svelte component has no knowledge that it is a custom element. The custom element wrapper takes care of handling its lifecycle appropriately.
61
+
62
+
When a custom element is created, the Svelte component it wraps is _not_ created right away. It is only created in the next tick after the `connectedCallback` is invoked. Properties assigned to the custom element before it is inserted into the DOM are temporarily saved and then set on component creation, so their values are not lost. The same does not work for invoking exported functions on the custom element though, they are only available after the element has mounted. If you need to invoke functions before component creation, you can work around it by using the [`extend` option](#component-options).
63
+
64
+
When a custom element written with Svelte is created or updated, the shadow DOM will reflect the value in the next tick, not immediately. This way updates can be batched, and DOM moves which temporarily (but synchronously) detach the element from the DOM don't lead to unmounting the inner component.
65
+
66
+
The inner Svelte component is destroyed in the next tick after the `disconnectedCallback` is invoked.
67
+
58
68
## Component options
59
69
60
-
When constructing a custom element, you can tailor several aspects by defining `customElement` as an object within `<svelte:options>` since Svelte 4. This object comprises a mandatory `tag` property for the custom element's name, an optional `shadow` property that can be set to `"none"` to forgo shadow root creation (note that styles are then no longer encapsulated, and you can't use slots), and a `props` option, which offers the following settings:
70
+
When constructing a custom element, you can tailor several aspects by defining `customElement` as an object within `<svelte:options>` since Svelte 4. This object may contain the following properties:
61
71
62
-
-`attribute: string`: To update a custom element's prop, you have two alternatives: either set the property on the custom element's reference as illustrated above or use an HTML attribute. For the latter, the default attribute name is the lowercase property name. Modify this by assigning `attribute: "<desired name>"`.
63
-
-`reflect: boolean`: By default, updated prop values do not reflect back to the DOM. To enable this behavior, set `reflect: true`.
64
-
-`type: 'String' | 'Boolean' | 'Number' | 'Array' | 'Object'`: While converting an attribute value to a prop value and reflecting it back, the prop value is assumed to be a `String` by default. This may not always be accurate. For instance, for a number type, define it using `type: "Number"`
72
+
-`tag`: the mandatory `tag` property for the custom element's name
73
+
-`shadow`: an optional property that can be set to `"none"` to forgo shadow root creation. Note that styles are then no longer encapsulated, and you can't use slots
74
+
-`props`: an optional property to modify certain details and behaviors of your component's properties. It offers the following settings:
75
+
-`attribute: string`: To update a custom element's prop, you have two alternatives: either set the property on the custom element's reference as illustrated above or use an HTML attribute. For the latter, the default attribute name is the lowercase property name. Modify this by assigning `attribute: "<desired name>"`.
76
+
-`reflect: boolean`: By default, updated prop values do not reflect back to the DOM. To enable this behavior, set `reflect: true`.
77
+
-`type: 'String' | 'Boolean' | 'Number' | 'Array' | 'Object'`: While converting an attribute value to a prop value and reflecting it back, the prop value is assumed to be a `String` by default. This may not always be accurate. For instance, for a number type, define it using `type: "Number"`
78
+
You don't need to list all properties, those not listed will use the default settings.
79
+
-`extend`: an optional property which expects a function as its argument. It is passed the custom element class generated by Svelte and expects you to return a custom element class. This comes in handy if you have very specific requirements to the life cycle of the custom element or want to enhance the class to for example use [ElementInternals](https://developer.mozilla.org/en-US/docs/Web/API/ElementInternals#examples) for better HTML form integration.
65
80
66
81
```svelte
67
82
<svelte:options
@@ -70,12 +85,35 @@ When constructing a custom element, you can tailor several aspects by defining `
// Extend the class so we can let it participate in HTML forms
91
+
return class extends customElementConstructor {
92
+
static formAssociated = true;
93
+
94
+
constructor() {
95
+
super();
96
+
this.attachedInternals = this.attachInternals();
97
+
}
98
+
99
+
// Add the function here, not below in the component so that
100
+
// it's always available, not just when the inner Svelte component
101
+
// is mounted
102
+
randomIndex() {
103
+
this.elementIndex = Math.random();
104
+
}
105
+
};
73
106
}
74
107
}}
75
108
/>
76
109
77
110
<script>
78
111
export let elementIndex;
112
+
export let attachedInternals;
113
+
// ...
114
+
function check() {
115
+
attachedInternals.checkValidity();
116
+
}
79
117
</script>
80
118
81
119
...
@@ -91,5 +129,4 @@ Custom elements can be a useful way to package components for consumption in a n
91
129
- In Svelte, slotted content renders _lazily_. In the DOM, it renders _eagerly_. In other words, it will always be created even if the component's `<slot>` element is inside an `{#if ...}` block. Similarly, including a `<slot>` in an `{#each ...}` block will not cause the slotted content to be rendered multiple times
92
130
- The `let:` directive has no effect, because custom elements do not have a way to pass data to the parent component that fills the slot
93
131
- Polyfills are required to support older browsers
94
-
95
-
When a custom element written with Svelte is created or updated, the shadow dom will reflect the value in the next tick, not immediately. This way updates can be batched, and DOM moves which temporarily (but synchronously) detach the element from the DOM don't lead to unmounting the inner component.
132
+
- You can use Svelte's context feature between regular Svelte components within a custom element, but you can't use them across custom elements. In other words, you can't use `setContext` on a parent custom element and read that with `getContext` in a child custom element.
0 commit comments