| 09:38 | <Jake Archibald> | annevk Domenic : When's the appropriate time to move the view transitions HTML monkey patches into the HTML spec? (https://drafts.csswg.org/css-view-transitions-1/#monkey-patch-to-rendering-algorithm) |
| 09:52 | <annevk> | Jake Archibald: if it's just "update the rendering" skipping multiple implementer interest might be okay as it's essentially just a registry thing at that point |
| 09:53 | <Jake Archibald> | annevk: Fwiw, Mozilla have a positive position now https://github.com/mozilla/standards-positions/issues/677. But I'm also happy not to rush the changes to the HTML spec. It isn't getting in the way, just want to make sure we integrate properly |
| 09:53 | <Jake Archibald> | (it'd be great to get a WebKit position 😀) |
| 10:41 | <Sam Sneddon [:gsnedders]> | Am I right in thinking that setTimeout(…, 0) isn't special-cased anywhere? Why did I think that 0 was special-cased here? |
| 10:43 | <Andreu Botella> | when the nesting exceeds some limit, the timeout is clamped to 4ms, but there's nothing specific to 0 |
| 10:43 | <Andreu Botella> | there is a 0 special case for JS's Atomics.waitAsync though |
| 10:51 | <Jake Archibald> | Step 5 https://html.spec.whatwg.org/multipage/timers-and-user-prompts.html#timer-initialisation-steps |