Pier Paolo Ramon

As you can see the configuration is split in: - `on`, called when attaching the event directly on an element, - `delegate`, called when attaching an event as a delegate,...

Let me state this more clearly: I’m not _asking_ for such a feature. No other modern framework supports those AFAIK because it brings imperative stuff in a purely declarative context,...

Also such events should be quickly detached and reattached when using arrows: ```js class DropArea extends JSXComponent { render() { return ( this.value = e.target.value } value={ this.value } />...

@bryceosterhaus Why is it needed? There’s nothing wrong with that same component in async (default) mode.

What’s the behaviour you’re having without synchronous updates?

Mhhh very bad indeed.

I leave my 2¢ here too: component registration is leaky (there’s a single component registry) and should happen exclusively when the developer understands the implications.

See errors such as: ``` customElements.define('x-x', class X extends HTMLElement {}); customElements.define('x-x', class X extends HTMLElement {}); ``` > Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': this name has...

_**Hint:** it will happen when multiple versions of the same component are loaded in the page._

Actually that's what happens already. AFAIK it's in the spec.