Stefan Schultze

BTW, the comment of the no-op "implementation" in Preact says that > In React, `flushSync` flushes the entire tree and forces a rerender. The latter one doesn't seem to be...

As commented in #3928, the flush of the queue actually doesn't have to be synchronous. The callback passed to `startViewTransition` can return a promise, [as described here](https://developer.chrome.com/docs/web-platform/view-transitions/#async-dom-updates-and-waiting-for-content). But I think...

@foxt You should do anything that will cause a render, like `setState`, in the async method passed to `startViewTransition`. If the render happens because of changed `props`, call `startViewTransition` in...

@JoviDeCroock I have seen that you have gone for the 32-bit integer solution, as opposed to just counting from `Number.MIN_SAFE_INTEGER` upwards. With 32-bit integers, there is a slight chance that...

@JoviDeCroock Sorry 😅

@nbalatsk-oracle @JoviDeCroock What about using BigInt for the counter if the browser supports it? BigInts have an arbitrary size and will never overflow, and also no strange things happen if...

Probably another issue, but isn't it problematic that, even in the original code, the `_attached` property is added to the event handler function? The same event handler might be added...

> @sschultze Is it really a problem? It seems that it does not really matter that the handler is shared as long as the _attached/_dispatched order is correct. Even if...

@nbalatsk-oracle A thought experiment: If it would indeed be 100% safe to share event handlers between nodes, and still always get the correct behavior here, then it would - as...