Noam Rosenthal

> Thanks for clarification! > > After looking further at the [Chromium Early Hints source code](https://source.chromium.org/chromium/chromium/src/+/main:content/browser/loader/navigation_early_hints_manager.cc;l=453;drc=68ddd902509f2655d2b16605abd1f1276226294f), "preload the scripts as if they were `preload`" is actually a tweaked version for...

Anyway, I can work on a PR along those lines, where early hints performs the `modulepreload` steps all the way until the response, and continues to [fetch the script graph](https://html.spec.whatwg.org/multipage/webappapis.html#fetch-a-modulepreload-module-script-graph)...

Created a [PR](https://github.com/whatwg/html/pull/7862) to try to express the proposal.

Also, how should `auto` pseudo-elements appear in `getAnimations({subtree: true})[...].effect.pseudoElement` ? Probably also as `auto`? Or as `*`?

> I think we should discuss in a call, it'll be a first to have an identifier potentially return animations for multiple pseudo-elements. To be clear, this is about returning...

> I'd be in favor in resolving if it's just for how to serialize (e.g. output). But 👎 to using `match-element` as input. We're on the same page, this is...

> `blocking=render` already allows a UA-defined timeout. Is this feature request because the timeout should be different for view transitions, or because it shouldn't block rendering at all if there's...

> Thinking about this from a user-centric angle using guidance like https://web.dev/articles/rail and even personal experience, I have to imagine there's a small range for a good default render-blocking timeout...

The failing WPTs reveal that this issue in fact needs a lot of spec work, see https://github.com/w3c/csswg-drafts/issues/9563

I love the use cases and the direction! One thing that struck me is that perhaps the center point can be the 0 of the timeline rather than the 50%?...