Opportunity to leave out the bad parts of DOM.

The [article](https://jasonformat.com/element-worklet/) 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.

No repository files or tests are named. Start by reading the linked Element Worklet article and inspect the existing WorkletElement API, then determine whether a limited DOM surface is feasible and define the API boundary that would count as done.

Escrito por el modelo de indexación a partir del texto del issue.