01:46
<GPHemsley>
oy, what a bulky test suite this is
06:45
<ondras>
a quick question -- how does a XHR interact with the content-disposition:attachemnt response header?
06:46
MikeSmith
XhmikosR howdy
09:45
<smaug>
Any folks from React here?
09:47
<hsivonen>
Domenic, gsnedders: https://github.com/whatwg/encoding/issues/57#issuecomment-308654813 indicates we should wait for r12a to address my claims of test suite bugs
09:47
<hsivonen>
Domenic: I commented LGTM to merge EUC-KR, Shift_JIS and Big5 tests
09:47
<hsivonen>
Domenic: thanks
13:04
<smaug>
#join #react
13:04
<smaug>
oops
16:44
<Domenic>
Twitter does not like square logos anymore... https://twitter.com/storagestandard
16:57
<hasather>
Domenic: Hey. I saw http://logs.glob.uno/?c=freenode%23whatwg&s=14+Jun+2017&e=14+Jun+2017#c1030325 `elements` does include form controls outside of the form though, test e.g. data:text/html,<form id=a></form><input form=a><script>alert(a.elements.length)</script>
16:58
<hasather>
is the spec wrong there? (The original question was http://logs.glob.uno/?c=freenode%23whatwg&s=14+Jun+2017&e=14+Jun+2017#c1030301)
17:08
<Domenic>
hasather: well, it looks like it's an interop issue; Edge at least gives 0 for that test case, although FIrefox and Chrome do give 1. Would you mind opening a spec bug so we can collect opinions from implementers?
17:15
<hasather>
Domenic: Edge doesn't support the 'form' attribute yet, see https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/7327649-add-support-for-the-form-attribute. I'll file a bug on the spec. Thanks.
17:16
<hasather>
Domenic: Actually noticed this when implementing the 'form' attribute in jsdom. :)
17:16
<Domenic>
oh i see :)
17:22
<jsbell>
Domenic: for the big5 PR - ping me when the CI finishes if I don't notice first
17:23
<Domenic>
jsbell: sounds good, will do
17:32
<hasather>
Domenic: https://github.com/whatwg/html/issues/2764
17:39
<Domenic>
hasather: awesome, will look into it
19:53
<Domenic>
hsivonen: if the numbers at https://travis-ci.org/w3c/web-platform-tests/builds/243381522 are any indication, good job on encoding_rs performance, FF nightly is taking like 3/5 of the time of Safari and Chrome
19:55
<Domenic>
(Although using Travis for perf comparison is probably dubious, given how it's subject to fluctuating cloud resources)
20:40
<Domenic>
jsbell: https://github.com/w3c/web-platform-tests/pull/6254 ready for review
21:07
<wanderview>
Domenic: is it safe to use async functions in WPT now?
21:07
<Domenic>
wanderview: yes, although Servo folks might be sad.
21:07
<wanderview>
Domenic: if spidermonkey has async functions, won't servo have them too?
21:08
<Domenic>
wanderview: servo updates spidermonkey rarely, if ever...
21:08
<wanderview>
Domenic: well, they can remedy it if they want then
21:08
<Domenic>
Indeed
21:08
<Domenic>
They might be sad, but it's not a blocker
21:08
<wanderview>
Domenic: no one is going to want to run this test anyway
21:09
wanderview
is testing about:blank replacement interaction with service workers.
21:09
<Domenic>
good times
22:11
<jyasskin>
Do folks have a favorite Jabber client? It looks like that's what the IETF uses...
22:14
<Domenic>
I used to use Trillian, but I can't imagine it's kept up with the times...
23:08
<jsbell>
Domenic: done
23:11
<jsbell>
Domenic: thanks for picking the tests up!
23:17
<Domenic>
:) they just seemed so close, and it was a shame to let them languish