07:17
<annevk>
Oooh, exciting
12:34
<annevk>
zcorpan++ for requestSubmit() tests review
13:04
<ondras>
class MyEventTarget extends EventTarget { constructor(stuff) { super(); } } <--- is this correct?
13:04
<ondras>
because Safari says "function is not a constructor (evaluating 'super()')"
14:00
<annevk>
ondras: if it runs in Firefox I'd say it is
14:00
<annevk>
(not the best answer, granted)
14:01
<ondras>
:)
14:01
<ondras>
yeah, it works in FF and Chrome
14:17
<annevk>
ondras: might wanna search bugs.webkit.org for EventTarget
14:17
<ondras>
annevk: okay, will try
14:31
<ondras>
perhaps this is somewhat relevant: https://bugs.webkit.org/show_bug.cgi?id=67312
14:31
<ondras>
will issue a new bug probably
14:33
<annevk>
ondras: https://bugs.webkit.org/show_bug.cgi?id=174313
14:33
annevk
searched for EventTarget, then inline search for constructor
15:02
<Domenic>
Gah why does the W3C stylesheet still do terrible things to tables. https://pr-preview.s3.amazonaws.com/heycam/webidl/pull/722.html#synthetic-module-records
15:08
<ondras>
annevk: ah. I searched for "EventTarget super"
15:08
<ondras>
:/
15:26
<Domenic>
TabAtkins: if you could provide some sort of quick fix for https://github.com/w3c/tr-design/issues/104#issuecomment-490950952, for specs which don't need to conform to pubrules (e.g. EDs, community group reports, IDEA status) that would be much appreciated.
15:37
<TabAtkins>
Domenic: Looking into it again. The problem is that the styling issue we're trying to solve is hard. :(
15:37
<Domenic>
TabAtkins: I mean it would be good enough for me if tables just weren't wrapped in overlarge, or if overlarge didn't do any centering at all.
15:38
<Domenic>
Thanks for looking at it though. It is like my number one problem reading specs these days. (Probably other people have many other problems...)
15:38
<TabAtkins>
The point of overlarge is to provide a scrolling wrapper, so a wide table doesn't screw up the entire spec when reading on mobile.
15:41
<Domenic>
Does it need to be a centered scrolling wrapper?
15:42
<TabAtkins>
(Tangent: IDL both includes all the ED stylings manually, *and* links to the W3C ED stylesheet. It looks like this is just a result of the webplatform boilerplate doing that for some reason: https://github.com/tabatkins/bikeshed/blob/master/bikeshed/boilerplate/webplatform/header.include . I should fix that and see if anyone else copypasted that same error.)
15:42
<Domenic>
Yes please, I was noticing something weird going on in that vein, but didn't dig in too hard.
15:42
<TabAtkins>
Domenic: People really like centered tables, ¯\_(ツ)_/¯
15:43
<Domenic>
Citation needed? They are pretty terrible in all fixed-width specs...
15:54
<annevk>
I should create a filter for sheriffbot I suppose
15:55
<annevk>
sleevi’s claim of it actually working is thus far proven false to me
15:58
<Domenic>
Ms2ger: https://webassembly.github.io/spec/web-api/ does not contain the words "ArrayBufferDetachKey"
15:59
<Domenic>
Ah, I think it was supposed to be https://webassembly.github.io/spec/js-api/
15:59
<Domenic>
I'll fix
15:59
<annevk>
I wonder if IDL detach was only ever used by HTML
15:59
<Domenic>
This seems possible
16:00
<Ms2ger>
Domenic, yes, should be js-api
16:00
<annevk>
Yeah, though maybe some audio thing detaches?
16:01
<Domenic>
Streams detaches, but uses ES directly
16:01
<annevk>
Does it anticipate throwing?
16:01
<annevk>
I guess everything using ES directly is also problematic
16:02
<Domenic>
It does not
16:03
<Domenic>
Streams needs editorial love
16:06
<annevk>
You gotta write up this “I’m on the IDL train now” post 😊
16:07
<Domenic>
Besides https://github.com/whatwg/streams/issues/963 ?
16:09
<annevk>
Domenic: yeah, more like a personal journey thing
16:10
<Domenic>
Yeah... Just gotta re figure out how my blog works
16:10
<annevk>
😊
16:28
<TabAtkins>
lol
16:28
<TabAtkins>
this is why i wrote myself a composer
18:01
<TabAtkins>
Oh man, I think I fixed the table CSS to satisfy every single design constraint we had.
18:02
<TabAtkins>
Gobbless display:grid
20:06
<dtapuska>
can someone explain "All same-agent Window objects together represent a group of Window objects that can synchronously access each other, though sometimes only after setting the document.domain attribute (in)appropriately." in the HTML spec to me... cause it seems the definition of "same-agent Window objects" doesn't contain the domain comparison
20:19
<Domenic>
dtapuska: looking
20:20
<Domenic>
dtapuska: it does contain the domain comparison in step 6
20:21
<dtapuska>
that is the comparison of the host attribute in the tuple
20:21
<dtapuska>
host and domain are different attributes in the security origin tuple
20:21
<dtapuska>
See definitions of https://html.spec.whatwg.org/#same-origin
20:21
<dtapuska>
https://html.spec.whatwg.org/#same-origin-domain
20:23
<dtapuska>
and https://html.spec.whatwg.org/#isplatformobjectsameorigin-(-o-)
20:23
<dtapuska>
I want to rewrite isplatformobjectssameorigin as if agent windows are the same.. but I can't because the definition of same agent windows seems flawed but the note talks about it
20:25
<Mek>
it can't just compare domain of the security origin, since it needs to allow any two origins that could end up same-origin-domain if their domain attribute was modified in some manner
20:26
<Mek>
i.e. the current value of the domain attribute is irrelevant
20:32
<dtapuska>
Ah I get it then... because in order to modify domain it needs to be same_site