02:51
<wanderview>
yhirano__: this might interest you: https://bugs.chromium.org/p/chromium/issues/detail?id=753646
03:04
<yhirano__>
wanderview: thanks
07:18
<MikeSmith>
KevinMarks_: rel=service.post apparently used by Google Blogger? (for a long time now)
07:18
<MikeSmith>
https://developers.google.com/blogger/docs/2.0/developers_guide_protocol
07:18
<MikeSmith>
but not mentioned anywhere on http://microformats.org/wiki/existing-rel-values
07:18
<MikeSmith>
immedidate context is https://github.com/validator/validator/issues/544
07:31
<a-ja>
MikeSmith, https://github.com/validator/validator/issues/545
07:32
<MikeSmith>
a-ja: thanks
07:32
<a-ja>
finally got an ID
07:35
<MikeSmith>
well then, welcome to github :)
07:46
<TimothyGu>
tobie: thanks for cleaning up my makeshift tests :)
08:03
<tobie>
TimothyGu: I'm essentially using this as an opportunity to figure out what's happening in his area of the spec. So thanks for that!
08:04
<tobie>
TimothyGu: FYI I'm ooo until Monday so don't expect a lot of movement until then.
08:15
<TimothyGu>
tobie: that's alright! I'll revisit the discussion you had with Domenic first
08:27
<tobie>
TimothyGu: Yeah. I was wrong btw. See the tests I added for [[Set]].
09:26
<a-ja>
it's about <time>
09:49
<MikeSmith>
annevk: thanks for responding on that SO question. I had forgotten about the event-listener thing
10:29
<MikeSmith>
annevk: As I just mentioned in the comment there I think we really need a note in the XHR spec explaining this. But despite having chatted with you know about this several times, I find I still don’t even know how to explain how the requirements in the current spec lead to this behavior
10:30
<MikeSmith>
annevk: I assume the relevant requirement is step 37 of https://fetch.spec.whatwg.org/#dom-request
10:30
<MikeSmith>
> If body is non-null and body’s source is null, then run these substeps:
10:30
<MikeSmith>
> Set r’s request’s use-CORS-preflight flag.
10:31
<MikeSmith>
(since that is the only place in the XHR spec where the use-CORS-preflight flag is set)
10:31
<MikeSmith>
but I have no idea how that relates to event listeners being set
10:32
<MikeSmith>
d’oh
10:32
<MikeSmith>
never mind
10:32
<MikeSmith>
I was looking at the fetch spec..
10:36
MikeSmith
decides that’s a sign it’s time for him to take a break
12:05
<nox>
⛔️
12:05
<nox>
MikeSmith: Like this?
12:20
<MikeSmith>
nox: :)
12:45
<JakeA>
annevk: I'm changing "A Response object also has an associated Headers object" to "A Response object also has associated headers, a Headers object", any objections? Doing the same for requests
12:45
<annevk>
JakeA: sure "a Headers object" could maybe be between parenthesis
12:46
<annevk>
that's mostly how we indicate types these days
12:46
<annevk>
though I suppose it varies
12:46
<JakeA>
Gotcha
14:13
<annevk>
JakeA: Edge is first to support abortable fetch?!
14:13
<annevk>
Weird, but also great
14:13
<JakeA>
annevk: I know right!! I was quite surprised
14:14
<JakeA>
I filed the bug but figured they'd get to it eventually
14:14
<JakeA>
one week later…
14:14
<JakeA>
Although I guess we'd need to see it to call them the winners :D
14:17
<annevk>
I suspect it'll be in Firefox Nightly somewhere in September, unless there's a lot of other things to take care of suddenly
14:17
<annevk>
I'll have another look at the spec tomorrow with Domenic's feedback in mind and also have a closer look at how it should work together with XHR
14:18
<JakeA>
annevk: I'll try to land some changes before then
14:18
<JakeA>
addressing Domenic's feedback now. But I kinda pulled on a string by adding headers to both request and response :D
14:19
<JakeA>
pulled on a thread
14:19
<JakeA>
whatever the saying is
14:19
<annevk>
JakeA: ah yeah, it might be worth landing that separately if easy to split
14:21
<JakeA>
annevk: I'm not sure it is, since it's part of clone() and the constructor
14:21
<annevk>
JakeA: I meant the initial change of turning it into a concept
14:21
<annevk>
which would be a purely editorial change
14:22
<JakeA>
annevk: I'll see if I can split it out
14:22
<gsnedders>
JakeA, annevk: I wonder if it's just simple-easy to do based on whatever Windows API they're using?
14:23
<JakeA>
should have thought about that earlier
14:23
<JakeA>
gsnedders: maybe… I guess it depends if the wired the service worker side in
14:30
<annevk>
From the speed I suppose it was somewhat easy in Firefox too, mostly delayed now due to vacation
14:30
<annevk>
But not sure if we got all the edge cases such as clone() correct
14:31
<JakeA>
Especially since it wasn't spec'd or tested
14:36
<annevk>
yup
14:48
<MikeSmith>
annevk: https://github.com/whatwg/xhr/pull/148 in hopes that it helps clarify things for people
14:49
<MikeSmith>
also I guess I should update the MDN CORS article to make it clear there too
17:00
<annevk>
MikeSmith: I'll have a look tomorrow, probably reasonable to have something
17:00
annevk
attempts to register the Refresh header with IANA
17:05
<annevk>
wanderview: slow clap for https://twitter.com/wanderview/status/895320296823046145
17:05
<annevk>
wanderview: that whole thread is amazing
17:32
<wanderview>
annevk: the funny thing (to me), is I actually saw the 7ms DOMContentLoaded first and was like "woah!"... then I saw the render... sad trombone...
17:33
<annevk>
heh
17:37
<wanderview>
annevk: and for what its worth the site totally does render with streams if I include the right patchset in my build
17:50
<TabAtkins>
Man tho, how'd they even get 7ms. I guess a SW doing the rendering?
17:51
<TabAtkins>
Here I am all proud of my blog getting content and first paint in 100ms and full rendering in 400. ^^_
17:52
<wanderview>
TabAtkins: yea, it was a service worker that was already running... and probably some lucky timing with main thread runnables
17:52
<wanderview>
TabAtkins: and it was the DOMContentLoaded number... I guess not first paint
20:49
<MikeSmith>
oh I like the background image of https://twitter.com/wanderview/
20:50
<MikeSmith>
wanderview: that’s from the imperial palace grounds?
20:50
<wanderview>
MikeSmith: thanks! yep! I took it the day before the service worker meeting in April
20:50
<MikeSmith>
ah super
20:50
<wanderview>
MikeSmith: btw, sorry I didn't really get to talk with you much at the meeting
20:50
<MikeSmith>
no worries, let’s talk more next time!
20:51
<wanderview>
cool... I'll be at tpac
20:51
<MikeSmith>
yeah me too
20:51
<MikeSmith>
let’s have another service worker meeting Tokyo
20:51
<MikeSmith>
actually I’d like we have a service worker meeting in China
20:51
<MikeSmith>
would be easy to arrange if the group wanted to
20:52
<wanderview>
I must admit the trans-pacific flights are not my first choice :-) but I know a lot of people have to make long trips, so I can't really complain
20:52
<MikeSmith>
yeah the flight part sucks
20:53
<wanderview>
"not in the usa" seems more likely in the future, though
20:53
<wanderview>
I'm guessing
20:54
<MikeSmith>
as far as China, having it in Hangzhou would make it more appealing than Beijing or elsewhere
20:54
<MikeSmith>
Hangzhou is Alibaba land
20:54
<MikeSmith>
HQ
20:55
<MikeSmith>
anyway btw Japan is a one of the likely candidate locations for TPAC 2019
20:55
<wanderview>
where is 2018?
20:56
<MikeSmith>
not sure it’s been announced yet
20:56
<MikeSmith>
in Europe, but unfortunately not in Lisbon
20:56
<MikeSmith>
tried to get it in Lisbon again but scheduling didn’t work out, we had a conflict with IETF the same week
20:57
<MikeSmith>
ah TPAC 2018 location was announced already
20:57
<MikeSmith>
Lyon
20:57
<MikeSmith>
which is very very nice too
20:58
<MikeSmith>
great food, beautiful old town
20:59
<wanderview>
cool
20:59
<wanderview>
I've never been... not quite sure what to expect yet
21:26
<TabAtkins>
wanderview: Some WG meetings, but the most useful part is all the "hallway meetings" you have with people. So many useful things come out of finally getting 5 minutes of face-to-face time with the right person.
21:35
<jgraham>
MikeSmith: Not sure Lyon isn't better than Lisbon
21:35
<jgraham>
Although Lisbon was also better than anywhere in the bay area, or China, or Hokkaido
21:36
<jgraham>
(I mean Japan is fun ofc, but Hokkaido in Autumn is not the best of Japan)
21:36
<jgraham>
Tokyo would be pretty great
21:37
<jgraham>
Probably won't go if it's in China again. Too much hassle for a place where the internet doesn't work
21:38
<jgraham>
(I appreciate Shenzhen is probably not the best of China)
21:38
<jgraham>
Anyway, nice to talk as if the world will still exist in two years and not be some nuclear wasteland
21:42
<jgraham>
Anyway these have been unsolicited opinions on TPAC locations
21:43
<jgraham>
One more: At least it isn't Orlando
21:45
gsnedders
probably wouldn't go if it were in China either
21:45
<gsnedders>
well maybe Hong Kong
22:23
<MikeSmith>
haha at least it isn't Orlando indeed
22:25
<MikeSmith>
anyway about TPAC, 100% agreed with TabAtkins about the bestest thing being hallway meetings, chance to talk with people in the real world
22:46
<gsnedders>
wait people exist in the real world
22:46
<gsnedders>
or is just ms2ger and bz that don't?