06:01 | <annevk> | Noam Rosenthal: "prepare to run script" |
06:09 | <Noam Rosenthal> | oh yea I see. thanks! |
11:15 | <Noam Rosenthal> | annevk: following up on your fetchLater comments, I don't know how to go about the thing about potentially trustworthy URLs |
11:16 | <Noam Rosenthal> | annevk: I can't handle it in the network layer, as the error has to be thrown synchronously. What I want to do here is allow HTTPS+localhost-ish URLs for fetchLater but nothing else... is that not possible to do synchronously? I didn't get why this was related to mixed content |
12:35 | <annevk> | Noam Rosenthal: okay, disregard that comment in that case; that's not quite the same as a Mixed Content check |
12:36 | <annevk> | I wish we had a better term than "potentially trustworthy" |
12:38 | <Noam Rosenthal> | "secure or local" |
12:46 | <Noam Rosenthal> | annevk: great. so I think everything else is fixed. Regarding the parameter name: activationTimeout seems like the wrong term, and it's pretty flexible to. be an activationDeadline . How about activationDelay ? |
12:52 | <annevk> | Noam Rosenthal: I can take a look tomorrow, it's a holiday here. A comment explaining why it's wrong and what the alternatives could be would help. |
12:55 | <Noam Rosenthal> | annevk: will do, enjoy the holiday, thanks for checking in. |
14:17 | <canadahonk> | Hey all, how are siblings defined in the processing model for user activation? The spec (https://html.spec.whatwg.org/multipage/interaction.html#user-activation-processing-model) says:
|
14:18 | <canadahonk> | eg a frame tree like
|
14:20 | <canadahonk> | interacting with iframe 1, should it set the ancestor (top), and in impl that itself sets all of it's descendants (iframe 2 etc)? |
14:58 | <canadahonk> | (also it doesn't include document's own/current window?) |