| 01:17 | <Domenic> | TabAtkins: annevk : this seems like a case for link-defaults, just on a larger scale? Like maybe all WHATWG specs get link-defaults for all HTML elements? Or maybe "all web specs", if we can operationalize that? Or even all Bikeshed specs, so that epub-related specs are the ones that need to override the link defaults? (But I'm not sure how such epub-related specs would necessarily find that out...) |
| 01:43 | <TabAtkins> | Yeah, I'm gonna have to figure something out. The big global namespace works adequately for W3C specs, but as more come online these sort of conflicts will happen more often. |
| 02:32 | <TabAtkins (Vacation until May)> | FYI, I'm on vacation until nearly the end of the month. |
| 06:09 | <annevk> | Luke Warlow: the parser change is tied to the other PRs as well, which is why I'd really like to see some kind of plan for landing these five PRs before signing off |
| 06:10 | <annevk> | Luke Warlow: for instance, the selectedoption PR also makes parser changes (and also impacts the content model) |
| 06:10 | <annevk> | Oh, I see jarhar did something like that now. Maybe that's easier to review. |
| 06:15 | <annevk> | Domenic: interesting, https://software.hixie.ch/utilities/js/live-dom-viewer/?.%3Cscript%3E%0Aiframe%20%3D%20document.createElement(%22iframe%22)%3B%0Aiframe.src%20%3D%20%22about%3Ablank%22%3B%0Adocument.body.append(iframe)%3B%0Aiframe.contentWindow.eval(%22self.globalSave%20%3D%205%3B%22)%3B%0Aiframe.onload%20%3D%20()%20%3D%3E%20%7B%0A%20%20w(%27load%27)%3B%0A%7D%3B%0A%3C%2Fscript%3E doesn't give a load event in Chromium/WebKit at all |
| 06:16 | <annevk> | And we did revamp open() to be a giant document state reset. Perhaps that was really the case that kept the weird Window : Document 1:2 relationship alive? |
| 06:17 | <Domenic> | Want to save that to a clickable link? |
| 06:17 | <annevk> | https://software.hixie.ch/utilities/js/live-dom-viewer/saved/13650 |
| 06:18 | <Domenic> | The load event fires synchronously: https://software.hixie.ch/utilities/js/live-dom-viewer/?saved=13651 |
| 06:18 | <Domenic> | I'm still a little confused on the relationship between load events and 1:2 Window:Documents... |
| 06:20 | <Domenic> | E.g. same-origin-initial.html in https://chromium-review.googlesource.com/c/chromium/src/+/804797 doesn't use load events at all and I think it's testing window object reuse. |
| 06:23 | <annevk> | Ah yeah it does. And if you set .src after connection it does take effect. I do see replacement then. https://software.hixie.ch/utilities/js/live-dom-viewer/saved/13652 |
| 06:28 | <annevk> | Domenic: that test is pretty clear, but it seems the PR got abandoned? I tried to find it on wpt.fyi but it's not there. |
| 06:29 | <Domenic> | Yes, I think Daniel was unsure what the spec expected exactly, and we didn't give him clear enough answers fast enough... |
| 06:33 | <annevk> | Ah, that's too bad. Is it easy for you to create a WPT PR out of those tests? |
| 07:56 | <Domenic> | Eh, I'd have to verify they match the spec, which could take some time... if there's traction on solving this problem I might make the time |
| 08:06 | <annevk> | Domenic: just a draft PR would be nice so we can see the results. |
| 08:07 | <annevk> | I'm not really committed to solving it just yet, but I'm interested in learning more. |
| 08:46 | <annevk> | Noam Rosenthal: the Deferred fetching PR logs a CI error |
| 08:47 | <annevk> | Noam Rosenthal: there's also very many unresolved comment threads (though it seems like you did address them, just not hit resolve) |
| 09:05 | <annevk> | Noam Rosenthal: in https://github.com/whatwg/html/pull/10903 I think you forgot to push |
| 09:06 | <annevk> | Generally it's a good idea to push before resolving as otherwise you have entered a race with the reviewer. (Which you lost this time around. 😛) |
| 11:23 | <Noam Rosenthal> | Hehe I actually pushed to my private repo and forgot that I used a branch in the whatwg repo for this one... but yea noted |
| 12:20 | <Noam Rosenthal> | All closed and no CI errors. |
| 12:25 | <annevk> | Noam Rosenthal: thanks, do you remember who we clash with on "allowed to use"? I wonder if that's an upstream bug. |
| 12:25 | <Noam Rosenthal> | Attribution reporting |
| 12:26 | <Noam Rosenthal> | sorry "private aggregation" |
| 12:26 | <Noam Rosenthal> | https://patcg-individual-drafts.github.io/private-aggregation-api/#privateaggregation-allowed-to-use |
| 12:40 | <annevk> | Noam Rosenthal: can you file a bug against them? They should have used "for" |
| 13:34 | <Noam Rosenthal> | It does have a for, but the links in fetch don't have a for=/ |
| 13:34 | <Noam Rosenthal> | https://respec.org/xref/?term=allowed+to+use looks right |
| 13:50 | <annevk> | Noam Rosenthal: ah okay, then we should update the links and not add a default |
| 13:51 | <Noam Rosenthal> | Right, I can prepare a small PR for the existing stuff and then update the fetchLater one |
| 13:51 | <Noam Rosenthal> | Or is this problem only in the fetchLater PR? |
| 13:57 | <Noam Rosenthal> | OK it's just in that PR, updated |
| 14:29 | <annevk> | Oh no, fetch.bs also can't compute blame anymore. |
| 18:45 | <zcorpan> | annevk: looks like various things on window are replaced by a javascript: document replacement: https://software.hixie.ch/utilities/js/live-dom-viewer/saved/13656 |
| 22:07 | <jmdyck> | In the ImageData commit that was merged into HTML yesterday, the "Initialize an ImageData object" algorithm no longer uses its 'defaultColorSpace' parameter. Seems odd. |
| 23:33 | <LI Daobing> | Hi, I think I found a bug in https://html.spec.whatwg.org/multipage/server-sent-events.html#parsing-an-event-stream , where could I report it? |