| 07:56 | <hsivonen> | annevk: what's the status of window.event spec? |
| 07:57 | <annevk> | hsivonen: the global question is still undecided |
| 07:57 | <annevk> | hsivonen: I wrote tests and such, but nobody is really weighing in on what to do |
| 08:29 | <hsivonen> | annevk: ok. thanks |
| 08:45 | <yoav> | annevk: I added about:blank handling to https://github.com/whatwg/html/pull/3714 PTAL? |
| 09:16 | <foolip> | PSA: web-platform-tests move happening today (2018-05-28) |
| 09:16 | <foolip> | https://lists.w3.org/Archives/Public/public-test-infra/2018AprJun/0014.html |
| 09:19 | <annevk> | foolip: hmm, but some of the PRs aren't ready yet it seems |
| 09:19 | <annevk> | foolip: e.g., https://github.com/tabatkins/bikeshed/issues/1224 |
| 09:20 | <annevk> | foolip: did you figure out the licensing thing you wanted to sort out? I'm curious to the outcome |
| 09:20 | <foolip> | annevk: yep, pretty much: https://github.com/w3c/web-platform-tests/issues/11009#issuecomment-391717229 |
| 09:21 | <foolip> | annevk: still some question about what to do with CONTRIBUTING.md, but nobody with legal chops suggested there was a blocking problem. |
| 09:23 | <foolip> | annevk: I'll chase down "w3c/web-platform-tests" until it's all updated, the Bikeshed one included. Since it requires regenerating to take any effect I didn't prepare it up front |
| 09:27 | <annevk> | foolip: left a comment on the license thing |
| 09:28 | <annevk> | yoav: done |
| 09:28 | <yoav> | annevk: Thanks! :) |
| 09:28 | <annevk> | yoav: I'm sorry this is still such a mess |
| 09:29 | <annevk> | yoav: I really want to fix the whole doc lifecycle, but I keep hitting walls and it's hard to make a lot of progress given that everyone is always busy |
| 09:29 | <foolip> | annevk: I thought I'd leave it to Wendy or PLH to send the PR, but that's presumably a good question there :) |
| 09:30 | <yoav> | annevk: can relate :) what's the best place for the about:blank processing? Is there some place central that handles that case for iframes as well as object/embed? |
| 09:31 | <yoav> | or I should just add another processing step for them as well? |
| 09:31 | <annevk> | yoav: I'm not sure, I'd have to research |
| 09:31 | <annevk> | yoav: part of the problem is that we don't have a "create an about:blank document" routine somewhere |
| 09:32 | <annevk> | (or even a proper "create a document"...) |
| 09:34 | <yoav> | annevk: makes sense. I don't see about:blank handling in embed, only in object |
| 09:35 | <annevk> | yoav: hmm yeah, <embed> in spec might be broken, so I guess just fixing it for <object> is acceptable |
| 09:35 | <annevk> | s/might be/is/ |
| 09:35 | <yoav> | ok, cool |
| 09:36 | <annevk> | not really 😃 |
| 09:36 | <yoav> | :) |
| 11:58 | <annevk> | JakeA: did you see https://github.com/whatwg/fetch/issues/706? |
| 12:42 | <JakeA> | annevk: I didn't, but I'll go through it tomorrow (bank holiday today). Thanks for the nudge |
| 13:08 | <annevk> | enjoy |
| 13:51 | <gsnedders> | is it defined anywhere what is considered a user-initiated event? |
| 13:52 | <annevk> | gsnedders: https://html.spec.whatwg.org/#triggered-by-user-activation |
| 13:53 | <gsnedders> | minor feedback: given we normally call it a user initiated event, it'd be nice for that phrase to appear in the spec |
| 14:03 | <gsnedders> | if you created a synthetic click event within a trusted click event's event listener, that would be untrusted, right? |
| 14:06 | <annevk> | gsnedders: I think that would still be trusted if you dispatch it within that listener callback |
| 14:08 | <gsnedders> | annevk: the only text I can see that might justify that is "The task in which the algorithm is running was queued by an algorithm that was triggered by user activation, and the chain of such algorithms started within a user-agent defined timeframe." but isTrusted on the event would presumably be false given nothing would set it to true? |
| 14:08 | <annevk> | gsnedders: yes and yes |
| 14:09 | <annevk> | gsnedders: there's open issues on formalizing this |
| 14:09 | <gsnedders> | But this is implemented everywhere? |
| 14:10 | <gsnedders> | issues on whatwg/html? |
| 14:10 | <annevk> | gsnedders: Chrome has been playing around with alternatives and I suspect there's differences in the details regardless |
| 14:10 | <gsnedders> | yeah, I mean at a high level |
| 14:10 | <gsnedders> | I don't doubt there are differences :) |
| 14:15 | <gsnedders> | https://github.com/whatwg/html/issues/1903 seems to mostly be it? |
| 14:25 | <annevk> | gsnedders: https://github.com/whatwg/html/issues/1983 and https://github.com/whatwg/html/issues/3123 are linked from there and seem relevant |
| 14:25 | <annevk> | gsnedders: I thought there were some others too, but maybe they've all been duped |
| 14:48 | <domfarolino> | foolip: If there's any work needed to make transition of WPT easier I'm happy to help feel free to lmk |
| 14:49 | <annevk> | domfarolino: all WHATWG repos need a PR to fix the README (and other links) |
| 14:50 | <annevk> | domfarolino: Bikeshed also needs some template updates |
| 14:50 | <annevk> | domfarolino: foolip: maybe we can combine this with the changes needed for Review Drafts since it's fairly minor |
| 14:50 | <annevk> | domfarolino: that would reduce the amount of Meta: changes by N |
| 15:04 | <domfarolino> | domfarolino: Oh nice, thanks. Combining the BS template changes sgtm btw |
| 15:53 | <devsnek> | on non-browser useragents (like node) should timers be able to keep the event loop alive |
| 15:53 | <devsnek> | assuming you don't have node's timer.ref/unref api |
| 17:52 | <domfarolino> | devsnek: That would make sense to me but I don't think I can provide a very "authoritative" answer |
| 17:53 | <devsnek> | rn I'm making them all refed |
| 17:59 | <domfarolino> | SGTM |
| 18:02 | <devsnek> | refed = Math.random() > 0.5 |