Open domenic opened 1 year ago
Especially complicated on a spec level, is that HTML currently will call "WebDriver BiDi navigation started" (and perhaps failed) synchronously, at the top level of navigate. Whereas checking whether or not we can do a prerendering activation will only be done in parallel.
So, if we were to want to do something besides the default WebDriver BiDi navigation started behavior, we'd probably need to move that callback to be in the parallel section too. Maybe that's fine?
The Browser Testing and Tools Working Group just discussed How should WebDriver BiDi expose prerendering activation?
.
In https://github.com/WICG/nav-speculation/ we're working on specifying prerendering. (Latest spec work, integrated with the recent changes to HTML's navigation algorithm, at https://github.com/WICG/nav-speculation/pull/207 .)
The tricky thing about prerendering is there are two "navigation"-type events:
On the spec level, the latter is done by hooking into the navigate algorithm, and instead of doing most of the normal stuff, instead activating.
HTML's navigate algorithm currently has a variety of WebDriver BiDi callbacks based on a given navigation ID. Should we have any for prerendering activation?