developit / element-worklet Goto Github PK

what's stage of this proposal is at w3c html wg?

The article mentions

What DOM APIs should be available to Element Worklet code? Can WorkletElement provide a sufficient API surface to allow current libraries and approaches to be reused with minimal modification?

This made me think that element worklets may provide an opportunity to provide only a subset of DOM APIs: only the good parts based on decades of learnings from main-thread DOM, dropping the bad parts.

A pattern seen in some custom element libraries is that they allow the end user to import the class, and for the end user to decide with which name to call customElements.define().

For example, an end user can do this:

import {NiceElement} from 'some-library'

// End user chooses the tag name:
customElements.define('cool-element', NiceElement)

const el = document.createElement('cool-element')

Maybe we should allow this pattern to still be possible with Element Worklets.

For that to be possible, maybe the worklet can call customElements.define like the proposal already shows, but maybe also the end user can call it if the worklet doesn't. The alternative form might look like this:

// nice-element.js

// Use a default export to denote the class for the ElementWorklet perhaps:
export default class NiceElement extends WorkletElement {...}

Then the end user can register the element:

// end-user.js
customElements.defineWorklet('cool-element', 'path/to/nice-element.js')

const el = document.createElement('cool-element')

Or maybe we can rely on the stage 3 import assertions proposal (I feel like the "import assertions" naming is strange). It could look like this:

// nice-element.js
// This is not a default export (the author can use any type of export):
export class NiceElement extends WorkletElement {...}

// end-user.js
import {NiceElement} from 'path/to/nice-element.js' assert { type: "element-worklet" }

// customElements.define would automatically know how to handle WorkletElement proxy classes:
customElements.define('cool-element', NiceElement)

const el = document.createElement('cool-element')

assert doesn't quite match the semantic though. It seems that assert is for asserting mime types, but the worklet would have the same mime type as any other JSON file. So maybe some other sort of "import attribute" would be needed in a follow on like that proposal mentions:

import {NiceElement} from 'path/to/nice-element.js' with { elementWorklet: true }

or something?