| 00:39 | <Steve Hicks> | that sounds useful, I was about to try to put something like that together myself |
| 18:19 | <Andreu Botella> | I'm looking at chromium event dispatch code, and it seems like there are a number of events (especially dealing with navigation, cross-window communication and similar things) that are synchronous if the window is active, but not if it's in the back/forward cache |
| 18:21 | <Steve Hicks> | That seems consistent with click, where it can be triggered either programmatically or by the user interface. Active vs fallback context should be fine? |
| 18:22 | <Andreu Botella> | could be |
| 18:23 | <Andreu Botella> | for the message event, though, chromium is already propagating the context for task attribution |
| 18:31 | <Andreu Botella> | huh, it seems like for at least some of these events with an async source, the way chromium dispatches them would make it easy to propagate the context in the implementation |
| 18:32 | <Andreu Botella> | but I don't know how that translates to other browsers, and that definitely does not translate to the specs |