Jason Miller

Feel free, I can barely remember what this was about by now, haha.

Yeah, I'm not sure I understand the motivation here. AFAIK useInsertionEffect is typically called once, and often invalidates styles asynchronously (by inserting a stylesheet or similar).

(FWIW I would like to add it!)

In this case, is `HTMLElement` the same as `JSX.HTMLElement`?

Definitely worth adding a note. Perhaps a page on the Preact site about usage with TypeScript? Or a .md here.

As per discussion with @surma, this likely circumvents the issue (but is not a solution): ```js const TestCe = 'test-ce'; const jsx = hai ``` (JSX turns any tagname with...

+1 to this - it seems like most of the UI toolkits built on Custom Elements have had to work around this, often by "patching" fields within shadow boundaries into...

There are a few reasons why I didn't include this type of registration behavior in the spec/demo: 1. Allowing registration on the main thread makes worklets main-thread-bound. That means worklets...

Note: this would be like setting browser support to "modern browsers and not IE"

I don't imagine this will move forward. Instead, we'll likely change the default behavior to use Babel's "automatic react runtime" mode, which imports `preact/jsx-runtime` automatically.