Andrea Giammarchi

@ije that's how custom elements work, the issue is that the error plugin includes again the whole package breaking in all possible ways: * the reference to hooks is not...

I’m OK if you remove the libraries you’ve mentioned as I’m not working much on these 👍

I was going to propose this flag myself, as people are "*scared*" by events delegation due flags, and not aware their library of choice might not even be usable in...

@krausest here we go: https://github.com/krausest/js-framework-benchmark/pull/1142 I've written some note there as the flag is actually all over the board but I've reasoned why I think that's actually the right choice,...

@yyx990803 this should've been amended after through automated tests, the initial PR simply looked for evaluation, it wasn't super accurate and few got removed (few others got added) later.

Hello there, I am struggling with this (imho) bug too and it's not clear to me at this point what `stderr` does, when, or if ever. Please allow me to...

@ryanking13 > think it's more natural to throw an exception than to print an error to stderr. in my example nobody can catch that error outside pyodide internals though ......

P.S. the main issue with `addEventListener('error')` is that it's really error prone (no pun intended): * any not caught error will pass through it, hard to make it robust for...

@hoodmane in my example the callback happens on click but the code enters and exits with no issue ... to clarify at least my thoughts: * the Python program should...

I don't get to know when these are unregistered and unless I take over (patch globally) `removeEventListener` it's pretty impossible but on top of that, DOM trash is a common...