Johan Gorter

@jcfranco The VNode should not be modified, once it is passed to maquette. Maquette keeps a reference to this VNode to do a diff during the next run. The wrapUp...

We decided it would benefit everyone if we finish the other 3.0 issues first, so everyone can profit from these and to delay this issue bit, because this has more...

Am I right that the only change for this to work would be a change to the Typescript definition of `VNodeProperties.on*` or do you need something more for this to...

Hmm, this would mean that the click handler should execute, only the `scheduleRender` will not be called automatically. This is worth investigating if we can make this work.

We have not encountered the usecases you mention, but they certainly seem valid. The `'on'+eventName` convention is simple, but not without limitations. What is most important for me, is a...

right now, maquette actually uses the attribute/property `onclick`, `on...etc` to register the eventhandler, instead of using `addEventListener`. This is the reason why focusin/out and custom events don't work. We could...

We actually have pieces of code that look like this, that would be more readable when eventListeners was a separate object, although most vnodes are less complex. ```ts { key:...

Sorry for the late reply. The separate object may be a little too complex for simple cases, so lets forget that idea for now. We could also consider using camelCase...

If we mark the old lowercase eventhandlers obsolete, most IDE's will add a strikethrough. This would minimize making mistakes I hope. DuringCapture was just a suggestion to make the code...

We have not found the time in our planning yet to implement this, but the need for this is becoming clearer, as custom elements are very promising. I am seeing...