| 17:37 | <Bakkot> | is there anyone here from the steering group who could provide an update on https://github.com/whatwg/sg/issues/63? |
| 17:40 | <jgraham> | https://github.com/web-platform-tests/wpt/blob/master/printing/print-microtask-after-navigate.html is there spec support for the idea that you can't call print when a document is unloading? |
| 17:40 | <jgraham> | Also I don't think the order of events in that test is what's claimed |
| 17:41 | <Domenic> | jgraham: only the fact that the first step is "The user agent may display a message to the user or return (or both)." |
| 17:42 | <jgraham> | Right, the spec always allows you to do nothing for print() |
| 17:43 | <jgraham> | Basically my question is "should I just delete that test, or is there actual value in it?" |
| 17:43 | <Domenic> | I mean, I assume there's value in testing for no crashes |
| 17:44 | <Domenic> | Probably worth asking the original author. |
| 17:48 | <jgraham> | Sure, there's always value in testing for no crashes, but at the moment the test times out in Firefox and Safari because they display a print dialog, so it's a rather expensive way to test that |
| 17:48 | <jgraham> | But OK, I'll ask the test author |
| 18:15 | <annevk> | Bakkot: I'm not sure they hang out here, I guess foolip and othermaciej sometimes do |
| 18:17 | <annevk> | Bakkot: I'd expect a bit more progress given https://github.com/whatwg/sg/issues/117#issuecomment-618033095, but probably still longer than desired |
| 18:17 | <annevk> | taking longer* |
| 18:20 | <Bakkot> | annevk: yeah, I'm mostly hoping to hear that it's something they're actively working on |
| 18:20 | <Bakkot> | the last message was in january promising updates |
| 18:20 | <Bakkot> | and it doesn't seem to have come up at the last meeting, per the notes |
| 18:21 | <annevk> | Bakkot: I suspect only https://github.com/whatwg/sg/issues/114 got tackled and this might take longer still, but I haven't asked anyone about it recently |
| 18:25 | <Bakkot> | yeah, and I'm glad to see progress on that one; unfortunately as editor of ecma-262 I am pretty firmly in the field of web technologies so it doesn't help me personally |
| 22:48 | <TimothyGu> | Domenic: for onerror, you could probably make the language a bit more precise using https://html.spec.whatwg.org/multipage/webappapis.html#event-handler-target? |
| 22:51 | <MikeSmith> | can somebody who has IE11 please test https://wpt.live/html/browsers/history/the-location-interface/location_origin.html and say what the result is? |
| 22:55 | <MikeSmith> | Bakkot: as an ecma-262 you might want to add info to https://github.com/whatwg/sg/issues/63 about how what the editors’ process is for identifying and handling non-normative changes |
| 22:55 | <MikeSmith> | in https://github.com/whatwg/sg/issues/63#issuecomment-570756354 I explained it as I understand it |
| 22:56 | <MikeSmith> | but the information would be more useful on record there coming from an actual editor rather than just me |
| 22:56 | <Bakkot> | MikeSmith I think your link to our contributor agreement is sufficient; I don't have anything to say beyond that |
| 22:57 | <MikeSmith> | ok |
| 22:58 | <MikeSmith> | anyway, thanks for not giving up on this, making an effort to get a response from the SG |
| 23:06 | <MikeSmith> | Bakkot: by the way, I am still lookin forward to a fix for that Salvation bug I reported :p |
| 23:07 | <Bakkot> | MikeSmith yeah, it's on my radar; I've just been working on a rewrite of it which has been taking up all the attention I've had for the project |
| 23:08 | <MikeSmith> | ok |
| 23:08 | <MikeSmith> | anyway, for the HTML checker I already have a workaround in place for now |
| 23:10 | <Domenic> | TimothyGu: that seems perfect, thank you |
| 23:47 | <MikeSmith> | interesting read https://lists.w3.org/Archives/Member/internal-gpu/2020May/0001.html |