08:16
<nox>
Should the quirkiness be preserved when serialising back a quirky length as per https://quirks.spec.whatwg.org/#the-unitless-length-quirk?
08:17
<annevk>
nox: I hope not?
08:17
<nox>
Well I hope so too.
08:18
<annevk>
Anyone want to do a final review of https://github.com/whatwg/whatwg.org/pull/25? Hopefully we can put it live by the end of the day
10:36
<nox>
annevk: Would you mind if I change unitless-length.html to not put all the properties in a single test?
10:38
<annevk>
nox: should prolly ask zcorpan
10:38
<nox>
For once that zcorpan isn't here, hah.
16:35
<TabAtkins>
miketaylr: Use example.com, like Domenic suggested.
16:36
<miketaylr>
ur not the boss of me
16:38
<TabAtkins>
Check your paystub again and get back to me.
16:39
<TabAtkins>
annevk: The conclusion of 5625 was "sounds good, we'll put it on gsnedders' backlog"
17:30
<gsnedders>
TabAtkins: what are you dumping on me? :)
17:30
<TabAtkins>
(Eventually) testing the UA stylesheet via getComputedStyle(). ^_^
17:30
<gsnedders>
TabAtkins: and what am I meant to be doing about this?
17:31
<TabAtkins>
Doing the thing. At some point, when it's worthwhile to point you at testing rather than testing infrastructure.
17:42
<gsnedders>
TabAtkins: and where is this tracked?
17:42
<gsnedders>
TabAtkins: because I don't see any bugs on wpt for this
17:43
<TabAtkins>
We chatted about it during the meeting, and Rick said he's down at some point.
17:43
<gsnedders>
Well that's an effective way to get it on my to-do list
17:47
<gsnedders>
TabAtkins: but seriously, it seems much better to file a bug so that other people know this is something we're missing and can potentially do something about
17:48
<TabAtkins>
Yeah, I get that. Not doing it right this moment.
19:05
<Domenic>
Isn't the bug filed? 5625?
19:05
<Domenic>
https://github.com/w3c/web-platform-tests/issues/5625
19:47
<TabAtkins>
Well there you go then.
21:49
<TabAtkins>
Any particular preference in APIs for takes-an-array vs takes-varargs?
21:50
<TabAtkins>
I'm writing up the proposed changes to TypedOM for calc, where we're switching calc()'s object to be an expression tree, and I need something like `CSSMathValue("+", 1em, 5px)`.
21:50
<TabAtkins>
And I'm wondering whether I should do those last bits as varargs, as in the example, or as `CSSMathValue("+", [1em, 5px])`.
21:51
<TabAtkins>
I think the latter is just excess wrapping for no good reason? Particularly since any browser with CSSMathValue will have the spread operator.
21:53
<Domenic>
I tend toward the array but I'm not sure why...
21:53
<Domenic>
We had some discussion about it for promises...
21:54
<TabAtkins>
In Promise.all there's a reasonable case for [] - the *output* is an array, so having the *input* be an array works, mentally.
21:54
<TabAtkins>
Here I'm just building a tree structure, and the latter arguments are the children for the node.
21:54
<Domenic>
Right, yep, that was it.
21:55
<TabAtkins>
(Also, in data structure terms, Promise.all is just the Traversable `sequence` operation, so having that represented correctly (going from Array<Promise<Foo>> to Promise<Array<Foo>>) is A+.)
23:23
<TabAtkins>
Is it possible to have an Array attribute in WebIDL?
23:23
<TabAtkins>
It *looks* like I can only do FrozenArray, which isn't what I want.
23:24
<TabAtkins>
(Given that I'd like to typecheck it, tho, I think I might need for the Array subclassing thing to resolve.)
23:30
<jsbell>
TabAtkins: You can do 'any' and define it in prose, of course; otherwise: don't think so (intentional restriction on sequence<>)
23:32
<TabAtkins>
kk.
23:32
<TabAtkins>
Given the typechecking, tho, I guess I can't really use Array anyway. :(
23:32
<TabAtkins>
I just replaced my nice typecheckable-at-mutation-time Maplike with something that contains an Array. :(