00:20
<domfarolino>
What exactly does the reference-implementation in whatwg specs help us do? Is it to help us understand what makes sense and what can be reasonably be implemented? is it often the origin for polyfills?
00:21
<Domenic>
domfarolino: the former. It also helps us write tests.
00:21
<Domenic>
Only streams really does it.
00:21
<Domenic>
jsdom/whatwg-url helps for whatwg/url, but is not official.
00:23
<domfarolino>
Oh yeah it's actually absent most of the time, didn't realize that.
00:24
<terinjokes>
console has tests done another way, but really awkward thing to test
00:24
<terinjokes>
since mostly side effects
00:31
<domfarolino>
gotcha
02:12
<MikeSmith>
Domenic: I guess I could write a separate special URL syntax checker but I use galimatias throughout the HTML checker source for other URL parsing, and its error reporting is pretty good so it’s seemed fine to just rely on that
02:19
<Domenic>
Yeah, hopefully the definition of valid URL doesn't change much
06:47
<annevk>
MikeSmith: yeah, I've asked Sebmaster to expose parse errors
06:47
<annevk>
MikeSmith: https://github.com/jsdom/whatwg-url/issues/61
06:48
<annevk>
MikeSmith: then https://quuz.org/url/uri-validate.html would work again
06:49
<MikeSmith>
cool
06:49
<MikeSmith>
oh I just went to https://github.com/jsdom/whatwg-url/issues/61 to give it a thumbs-up but it says I already did that
07:10
<zcorpan>
https://w3c.github.io/browser-payment-api/#idl-index has trailing commas in idl enums. that's invalid, right?
07:25
<annevk>
zcorpan: no
07:26
<annevk>
zcorpan: pretty sure that was never fixed and I don't think we necessarily should either
07:27
<zcorpan>
annevk: https://heycam.github.io/webidl/#idl-enums i don't see it allowing trailing comma, but maybe I'm missing something
07:27
<annevk>
zcorpan: sorry, I thought you said valid
07:27
<zcorpan>
ah
07:28
<annevk>
zcorpan: haven't had caffeine-free tea yet
07:29
<zcorpan>
annevk: does the tea help?
07:30
<annevk>
zcorpan: can I blame old age?
07:31
<zcorpan>
sure thing :-)
08:42
<annevk>
zcorpan: do we use the compat label also for interop issues?
08:43
<annevk>
zcorpan: I guess we don't really
08:44
<zcorpan>
annevk: don't think so, more compat with web content
10:30
<MikeSmith>
annevk: which part of the UTF-8 decode algorithm in the Encoding spec causes the BOM to be stripped?
10:31
<MikeSmith>
oh
10:31
<MikeSmith>
I guess just step 3
10:32
<MikeSmith>
> If buffer does not match 0xEF 0xBB 0xBF, prepend buffer to stream
10:33
<Ms2ger>
Yep
10:35
<MikeSmith>
thanks
12:28
<annevk>
t.unreached_func cool
15:24
<Sebmaster>
Ooooh. We can just expose an export which returns from the private API. Would that work for you annevk?
15:25
<annevk>
Sebmaster: yeah, I'd be happy to use the private API for that use case
15:25
<annevk>
(I might need some help with regards to how to make that work, but that'd be great to have)
15:26
<annevk>
Then we basically have a Live URL Validator
15:37
<annevk>
When you think software should be decimal-based: https://twitter.com/CodaCoder/status/840205916435705856
15:49
<annevk>
Anyone else having trouble with irc.w3.org?
15:54
<Domenic>
The problem is whatwg-url only implements a random subset of the validation errors
16:19
<astearns>
annevk: I'm not able to connect to irc.w3.org either
16:29
<Ms2ger>
Likewise
17:48
<annevk>
ta
17:57
<annevk>
Anyone interested in reviewing https://github.com/w3c/web-platform-tests/pull/5115? Main blocker to landing standard changes to align all header value separating on ", " (except for CORS, which will not use the space...)
17:58
<annevk>
My go to victims have been Domenic and foolip, but there must be more people out there
18:00
<annevk>
Domenic: ta
18:01
<annevk>
Guess I'll start filing some browser bugs
18:01
<Domenic>
that one was pretty easy :)