07:02
<annevk>
jyasskin: what gsnedders said; SHOULD means you MUST, unless you have a very compelling reason not to
10:10
<tobie>
annevk: should infra define what it means for a string to be equal to another string or is that too obvious?
10:11
<tobie>
annevk: WebIDL uses "=" and "≠" in some places for that, which I find sort of weird.
10:13
<annevk>
tobie: there's an issue on defining "is" I think, we haven't really made up our minds
10:13
<annevk>
tobie: I do think it would be good, since it gets more complicated as the types get more complicated
10:13
<tobie>
annevk: agreed
10:14
<tobie>
annevk: did you get my hangout answers now?
10:19
<annevk>
tobie: I replied 13min ago, nothing after that
13:00
<GPHemsley>
why did Chromium just merge in a wpt test for HTMLMenuItemElement.label? o_0 https://github.com/w3c/web-platform-tests/pull/6608
13:03
<annevk>
GPHemsley: it seems from https://github.com/w3c/web-platform-tests/pull/6608#issuecomment-317548169 that this was something old?
13:03
<annevk>
GPHemsley: and indeed probably obsolete now
13:03
<annevk>
GPHemsley: email https://lists.w3.org/Archives/Public/public-test-infra/ or file an issue?
13:08
<GPHemsley>
ah
13:35
<tobie>
GPHemsley: file an issue
16:46
<a-ja>
is <script nomodule> stable-ish?
17:05
<annevk>
a-ja: should be
17:06
<annevk>
a-ja: https://github.com/whatwg/html/issues?q=is%3Aopen%20nomodule confirms
17:06
<a-ja>
annevk: tks
17:09
<a-ja>
annevk: i found it a convenient place to stuff html5shim, rather than in IE conditional comments
17:10
<a-ja>
makes IE11 Emulation Mode happy :)
19:27
<tobie>
WebIDL uses a bunch of lists expressed as |list|<sub>0..|n|−1</sub>. Should this notation (or a variation of it) make its way into infra somehow?
19:28
<Domenic>
No, I hate that notation
19:28
<Domenic>
We should use |list|[|x|] as infra defines, instead of |list|<sub>|x|</sub>
19:34
<tobie>
Domenic, so I agree on the latter.
19:34
<tobie>
(Well the former too, I find it really hard to read)
19:42
<tobie>
Domenic: Oh wait, just realized the 0..n-1 notation is actually just a basic list. Had somehow assumed it was used to take a slice of the list without the last item.
19:42
<tobie>
Domenic: that totally proves your point. :D
19:43
<Domenic>
:)
19:50
<tobie>
Domenic: wow some bits are not trivial to change to a more readable notation
19:51
<tobie>
e.g. 5.5.1 of https://heycam.github.io/webidl/#dfn-effective-overload-set
19:52
<Domenic>
tobie: add a step, let m be list's size?
19:54
<tobie>
Domenic: now I actually have to understand what the algorithm does.
22:35
<weinig>
Domenic: tobie: Do either of you know if it is valid / meaningful for the Body interface in Fetch to reference ReadableStream in IDL, even thought ReadableStream has no IDL interface (as far as I can tell)?
22:45
<Domenic>
weinig: it is not really valid or meaningful; we are being sketchy about it.
22:45
<weinig>
Domenic: ok
22:45
<weinig>
Domenic: it’s gunking up my processor, but it’s cool
22:46
<Domenic>
weinig: I think in Chrome we did typedef object ReadableStream (or the other way around, I always forget which order typedef works in)
22:46
<weinig>
Domenic: seems fair
22:47
<weinig>
Domenic: is there a long term goal of having ES pick up Streams or something?
22:47
<weinig>
Domenic: it’s a bit odd that it doesn’t use WebIDL
22:48
<Domenic>
weinig: more a goal of staying environment agnostic, but since it was conceived I am no longer sure that choosing ES spec style was the right way to do it.
22:48
<MikeSmith>
botie, inform novalinium here now
22:48
<botie>
will do
22:49
<weinig>
interesting background, thanks
22:49
<Domenic>
weinig: https://github.com/whatwg/streams/issues/732 and https://github.com/whatwg/streams/issues/45 have more... yeah, still not really sure what the correct path was here