| 07:16 | <Sam Sneddon [:gsnedders]> | what in the HTML spec defines that setTimeout(function(x){ alert(1) }, 10000); window.location = "about:blank" won't actually create that alert after 10s? is this just step 1 of the in parallel section of https://html.spec.whatwg.org/multipage/timers-and-user-prompts.html#run-steps-after-a-timeout? |
| 07:17 | <annevk> | Sam Sneddon [:gsnedders]: I think the task will be associated with a document that's not fully active and thus will be skipped in the event loop processing model |
| 07:19 | <annevk> | Perhaps "cannot show simple dialogs" should also have a fully active check though. Not sure what happens if you run alert() on a window of a removed nested document. |
| 07:20 | <annevk> | https://software.hixie.ch/utilities/js/live-dom-viewer/saved/13247 suggests we should probably add that check. |
| 07:24 | <annevk> | Filed https://github.com/whatwg/html/issues/10742 |
| 07:24 | <Sam Sneddon [:gsnedders]> | My actual context here, FWIW, is figuring out what should happen if you do WebDriver's session.execute_async_script("setTimeout(arguments[0], 10000); window.location = 'about:blank'"), and whether that is actually well-defined. |
| 07:25 | <Sam Sneddon [:gsnedders]> | Thus my question here is mostly where it's defined where the handler is called. |
| 07:28 | <annevk> | Which handler? |
| 07:37 | <Sam Sneddon [:gsnedders]> | the TimerHandler (the first argument to setTimeout) |
| 07:39 | <annevk> | I think that's well-defined along the lines I said above, yes. |
| 09:20 | <zcorpan> | annevk: is the iteration order of the inclusive ancestors undefined in https://dom.spec.whatwg.org/#ref-for-concept-tree-inclusive-ancestor%E2%91%A1 ? |
| 16:48 | <TabAtkins> | Correct, there's no predefined order for inclusive ancestors, the spec needs to specify whether it's top-down or bottom-up |
| 18:02 | <annevk> | Yeah, that should say something about order. |