01:37
<MikeSmith>
I’m curious why the Safari team chose to prioritize implementation of navigator.sendBeacon over other things
01:37
<MikeSmith>
context being, it’s one of the features that shipped in the latest Safari Technology Preview
01:37
<MikeSmith>
https://developer.apple.com/safari/technology-preview/release-notes/
01:37
<MikeSmith>
maybe that have some particular use for it
01:38
<MikeSmith>
I don’t know enough about teh use cases for sendBeacon to be able to guess at what that might be though
01:39
<MikeSmith>
I guess the level of effort for implementing it might be significantly lower relative to a lot other things
07:11
<annevk>
MikeSmith: could also be something like Facebook saying they need it
08:16
<MikeSmith>
annevk: ah yeah
08:55
<foolip>
Regarding https://github.com/whatwg/whatwg.org/pull/36, where should we put the HTML FAQ? annevk Domenic MikeSmith ^
08:55
MikeSmith
looks
08:56
<foolip>
An FAQ.md in https://github.com/whatwg/html/ perhaps? We don't really have another place to put things....
08:59
<MikeSmith>
foolip: yeah that
08:59
<botie>
yeah that is definitely an algorithm.
08:59
<MikeSmith>
I think that would be fine
08:59
<foolip>
MikeSmith: ok, so converting to markdown then...
09:00
<MikeSmith>
thanks for doing the work on that
09:03
<foolip>
MikeSmith: has bob asked you to push all the buttons needed to launch the new PR results app?
09:06
<MikeSmith>
foolip: he has the power
09:07
<MikeSmith>
to do it all
09:07
<MikeSmith>
can’t recall what it’s waiting on at this point but not me
09:11
<annevk>
foolip: yeah I guess that's reasonable for now
09:11
<foolip>
annevk: working on it
09:48
<MikeSmith>
getting a “Rats! WebGL hit a snag.” message in Gmail and now curious to find out what Gmail is using WebGL for
10:08
<foolip>
annevk, MikeSmith: https://github.com/whatwg/html/pull/2903
10:10
<foolip>
parts of the FAQ feel a bit dated, should we add a warning to say that it's being revised, or something like that?
10:10
<foolip>
to not give the impression that touching it again is a re-commitment to everything it says
10:11
<annevk>
You should feel free to update it
10:11
<annevk>
Though maybe as a separate commit?
10:12
<foolip>
annevk: yeah, actually reading it and making it more approachable would be more work than I'm signing up for today, thought I'd just spend a few hours
10:39
<MikeSmith>
merged
10:40
<MikeSmith>
if you don’t have time soonish, I can volunteer to take a shot at updating it, especially the dated parts you mentioned
10:44
<JakeA>
annevk: I went for "associated headers" rather than "an associated headers" as the latter sounds clunky, but I guess it's customary to treat the property "headers" as a singular?
10:55
<annevk>
JakeA: yeah
10:56
<JakeA>
cool, I've made that change
11:20
<foolip>
MikeSmith: thanks for review! and I don't plan to spend time on updating it soon, so that'd be much appreciated
11:21
<foolip>
MikeSmith: https://github.com/whatwg/whatwg.org/pull/36 is now also in good shape
11:22
<foolip>
MikeSmith: in particular, the "other specifications" bit is a bit wrong towards the end now
11:22
<foolip>
MikeSmith: and the overall structure is strange
13:24
<annevk>
JakeA: so what's the idea about how the termination reason bubbles back up to the API?
13:44
<JakeA>
annevk: I'm struggling to find a use for termination reason
13:44
<JakeA>
annevk: maybe it'll become useful again with FetchObserver?
13:47
<annevk>
JakeA: as I pointed out XHR uses it
13:48
<annevk>
JakeA: the other question is whether any termination is an "AbortError"
13:50
<JakeA>
annevk: right now it's only AbortError via the signal
13:50
<JakeA>
TypeError otherwise
13:51
<JakeA>
annevk: maybe it's best to replace termination reason with something else?
13:53
<annevk>
JakeA: that's fine, as long as we don't break XHR
13:54
<JakeA>
annevk: right now, if you otherWindow.fetch() and that window goes away, it's a TypeError rather than an AbortError
15:06
<gsnedders>
is https://www.w3.org/TR/uievents/ the old DOM Level 3 Events spec?
15:06
<Ms2ger>
Yes
19:11
<miketaylr>
what's the story w/ https://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-September/033196.html being down?
19:12
<miketaylr>
any mirrors?
19:16
<miketaylr>
ah ok found it
19:16
<miketaylr>
hosted on lists.w3.org
21:54
<MikeSmith>
miketaylr: yeah some Dreamhost limitation prevents the lists.whatwg.org archives from working with TLS
21:54
<MikeSmith>
I think the only way we could fix it is to move whatwg.org to a different hosting service