Andrea Giammarchi

> Is there a use case that demands synchronous code? anything dealing with events on the DOM side, as there's no way to invoke `stopPropagation()` or `preventDefault()` in an async...

FWIWI *MicroPython* in *WASM* also supports this syntax and it's great to see alignment around this tiny, yet huge, detail. Thank You!

what's blocking this to be part of the docs? Also, I've just flagged the module as outdated, as it's 0.1.5 instead of 0.1.12 ArchLinux is increasily popular, also thanks to...

0.4 didn’t fix what it was supposed to fix so it didn’t go out. Tressa works with every engine and browser out of the box now. Exporting it as ESM...

@sorvell I think this answers already: https://github.com/tc39/proposal-signals/issues/185 in a graph where signals are shared and everyone is an owner of the value (as it can change it) those just reading...

P.S. previous art work, the *MutationObserver* doesn't ask users to guard its operations, these are already queued internally and fired "*at the best time*" ... here the API really impose...

as one that has been using *MO* forever (polyfills included) I never even thought the leaky records would be a problem but I fully agree with this issue concerns and...

:+1: for `.flush()` and dare I say `.detach(element)` or `.unobserve(node)` would be a nice extra things to the MO API. **edit** if there's any doubt around why the `flush()` is...

As author of all polyfills from v0 to current state, I fully support this proposal. My workaround is not super slow but it requires me patching the global `attachShadow` method...

As WebKit / Safari is landing [scoped Custom Elements](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md) we should be careful with polyfills or observing custom elements in there because the inner registry might already know, or take...