| 17:03 | <annevk> | Domenic: maybe an initial goal should be to just get a decent overview of document state APIs may depend on: bfcache/fully active/prerender/focused/visible? |
| 17:04 | <annevk> | And yeah, delay makes sense to me given that the event loop runs. |
| 17:12 | <Domenic> | annevk: yeah I like that goal. Especially now that we have things like system focus more well-defined. |
| 17:12 | <Domenic> | User activation is another one we found, e.g. a lot of APIs needed no changes for prerendering since they were dependent on user activation which can never happen while prerendered. |
| 17:14 | <annevk> | Domenic: hmm, I guess that depends on how user activation delegation works, does that do some kind of same TLBC check? |
| 17:14 | <Domenic> | Well we made prerendering BCs top-level BCs so I think it wouldn't impact it? |
| 17:14 | <annevk> | Oh, and even with that it might go wrong? If the same TLBC is used for the prerendered doc? Or maybe that doesn't work. How does that work? 🙂 |
| 17:15 | <Domenic> | They get an entirely separate TLBC |
| 17:15 | <annevk> | Domenic: so if you prerender a same-origin doc and then navigate to it, you break opener relationships? |
| 17:16 | <annevk> | Anyway, it would still require user activation delegation to do a TLBC check but I guess it already has to. You don't want it to travel to some other tab. |
| 17:16 | <Domenic> | Yeah I think that's the current plan, like a COOP switch |
| 17:17 | <Domenic> | Let me double-check... |