d26db282c6
Before this, there was a delay between when a queued microtask is finished, and it being marked as so. If an update was queued in between this delay, it would have been missed. This wasn't caught until now, because usually in a large react tree, usually there are one or more tickers that flush the queue, so if an update isn't picked up on one flush, it would end up in the next flush. |
||
|---|---|---|
| .. | ||
| benchmarks | ||
| browser-bundles | ||
| dataverse | ||
| dataverse-experiments | ||
| playground | ||
| r3f | ||
| react | ||
| theatric | ||