01:24
<MikeSmith>
does “x” part of “dppx”, “x” at https://drafts.csswg.org/css-values/#x mean that media (min-resolution: 2dppx) { ... }
01:25
<MikeSmith>
oofs
01:25
<MikeSmith>
.. mean that media (min-resolution: 2dppx) { ... }
01:25
<MikeSmith>
sigh
01:25
<MikeSmith>
.. mean that media (min-resolution: 2x) { ... } is valid?
01:26
<MikeSmith>
2x and 2dppx are equivalent?
01:54
<TimothyGu>
fun fact of the day: the only setter defined in ECMA-262 is Object.prototype.__proto__
03:02
<Domenic>
MikeSmith: omg. Gaaahhh I gotta make time to get that all merged.
03:08
<MikeSmith>
Domenic: no rush I may be futzing with it further
03:09
<MikeSmith>
I want to get feedback from TabAtkins on it, in the context of adding similar support in Bikeshed
03:11
<Domenic>
Yeah makes sense
06:36
<annevk>
Domenic: only cookies leak across the scheme-boundary afaik
06:37
<annevk>
Domenic: since new things are SecureContext that should remain so…
08:37
<nox>
A `long` argument accepts `Infinity` just fine, right?
08:37
<nox>
https://html.spec.whatwg.org/multipage/canvas.html#2dcontext:dom-context-2d-putimagedata
08:38
<nox>
https://github.com/web-platform-tests/wpt/blob/master/2dcontext/pixel-manipulation/2d.imageData.put.nonfinite.html#L23
08:38
<nox>
Is the spec or the test wrong?
08:38
<annevk>
I dunno, float/double has an unrestricted variant
08:39
<annevk>
Not sure why long is designed differently, probably because this came later...
08:39
<nox>
Yeah but those are longs.
08:41
<annevk>
nox: if there are no extended attributes my reading of https://heycam.github.io/webidl/#abstract-opdef-converttoint suggests you should get +0
08:42
<nox>
Yeah I doubt the conversion code we use in Servo is wrong, so either a spec or test bug. Given all browsers pass the test I guess it's a spec bug.
08:43
<Ms2ger>
nox, no, Infinity wraps to 0
08:43
<nox>
That's what I'm saying.
08:44
<nox>
I'm curious how https://github.com/whatwg/html/commit/362c9315971af63dbba49ef171644312c721444f landed when the TypeError throw test is right there already.
08:45
<Ms2ger>
Oh, wait
08:45
<annevk>
Could it be that putImageData was float-based before?
08:45
<nox>
Ah Chrome doesn't pass the test.
08:45
<annevk>
Ah, you pointed to that commit
08:46
<annevk>
nox: it seems those tests were forgotten when other tests were updated
08:47
<Ms2ger>
There we are
08:49
<nox>
So the tests are wrong?
08:49
<Ms2ger>
Yes
08:51
<annevk>
Aah, pre-browser bug era
08:51
<annevk>
Bad
08:51
<nox>
Pre-browser?
08:51
<Ms2ger>
pre-(browser bug)
08:52
<Ms2ger>
Or more specifically, before the policy of filing browser bugs
09:02
<nox>
Another question,
09:02
<nox>
why is this line supposed to do something? https://github.com/web-platform-tests/wpt/blob/master/2dcontext/pixel-manipulation/2d.imageData.put.dirty.rect2.html#L33
09:03
<nox>
if dx = -20 and dirtyWidth = 20, wouldn't everything that needs to be drawn fall outside the canvas surface?
09:06
<nox>
"For all integer values of x and y where dirtyX ≤ x < dirtyX+dirtyWidth and dirtyY ≤ y < dirtyY+dirtyHeight, copy the four channels of the pixel with coordinate (x, y) in the imagedata data structure's Canvas Pixel ArrayBuffer to the pixel with coordinate (dx+x, dy+y) in the rendering context's output bitmap." Am I being dumb?
09:07
<nox>
Oh yes I am, completely misread that.
13:40
<gsnedders>
can anyone remember why <!doctype> wasn't used? IIRC, it put IE/Mac into quirks, but I can't find a citation for that?
13:53
<annevk>
gsnedders: based on my blog post I tried to find corresponding mailing list discussion and I couldn't find any
13:53
<annevk>
gsnedders: I'm not sure I tried to trace IRC
13:53
<gsnedders>
annevk: searching for it is way too hard given search engines and punctuation :(
13:53
<annevk>
gsnedders: but I basically lost the plot how we decided on this
13:53
<annevk>
other than the blog post I wrote, which is easy to find
13:54
<gsnedders>
I'm pretty sure I remember <!doctype> being discarded because it put some UA into quirks.
13:54
<annevk>
clearly I should link more
13:56
<annevk>
So Firefox, unlike Chrome and Safari, does discard empty headers when combining multiple headers, that's nice
13:58
<annevk>
Edge does it wrong too, hurray
13:58
<annevk>
To be fair, neither Fetch nor XHR says anything about this
17:57
<Domenic>
annevk: were you going to finish https://github.com/whatwg/html/pull/3656 ?
18:50
<TabAtkins>
Domenic: There's no way to "export" from an inline module script, right? (Or equivalently, to set something on the global, without a cooperating non-module script?)
18:52
<TabAtkins>
Oh dang, never mind, I must have mistyped or something. You do have access to `window`, so you can explicitly set things on it that'll be visible to the rest of the page.