08:18
<tobie>
domfarolino: wrt to add namespace support to idlharness: it's going to be a bit involved.
08:21
<tobie>
domfarolino: you'll want to create a dedicated constructor IdlNamespace, that inherits from IdlObject just like IdlInterface does: https://github.com/w3c/web-platform-tests/blob/master/resources/idlharness.js#L880
08:22
<tobie>
Maybe you even want some kind of extra abstract class that both IdlNamespace and IdlInterface inherit from.
08:23
<tobie>
And then you'll want to hook it in properly, notably here: https://github.com/w3c/web-platform-tests/blob/master/resources/idlharness.js#L198
08:32
<tobie>
domfarolino: moved the above comments to the GH issue: https://github.com/w3c/web-platform-tests/pull/7551#issuecomment-336817155
10:12
<tobie>
ricea: you can trigger pr-preview by editing ever slightly the body of an existing PR (just add a linebreak)
10:16
<tobie>
ricea: yup, just noticed.
13:10
<domfarolino>
tobie: awesome thank you!
13:11
<domfarolino>
annevk: the Request domintro should contain attributes/methods that also appear in the Body interface since it implements it right?
13:12
<annevk>
domfarolino: hmm, I'd be okay with listing those under Body
13:12
<domfarolino>
Ok
13:12
<annevk>
domfarolino: so we don't have to duplicate between Request/Response
13:14
<domfarolino>
annevk: Ok that makes sense, I've updated https://github.com/whatwg/fetch/issues/543#issuecomment-336784513 to include a checkbox for the `RequestInit` members to be added to domintro so that is tracked independently of the current PR
13:18
<annevk>
domfarolino: okay, that violates how I think tree-style checkboxes should behave, but I'll allow it
13:19
<annevk>
domfarolino: so I'll land this then?
13:19
<domfarolino>
Ah yes it doesn't make too much sense as is. Sure if the nits and everything look good I think it's ready!
13:21
<annevk>
domfarolino: thank you!
13:29
<domfarolino>
annevk: NP thanks!
13:43
<domfarolino>
annevk: regarding your comment about using `getComputedStyle` on my wpt PR...wouldn't testing if the styles applied just be like testing that the browser properly downloads a regular style sheet with no media attr specified? As in, it doesn't seem to be testing what the HTML PR proposes right?
13:44
<domfarolino>
Though I guess it would be a little stronger than "document.styleSheets.length == 1" hm
13:45
<annevk>
domfarolino: you basically don't want to assume a particular impl
13:45
<annevk>
domfarolino: e.g., browsers could accidentally lie about document.styleSheets or it could reflect the second stylesheet being applied and not the first
13:45
<annevk>
domfarolino: so more assertions is better, if you can make them
13:45
<annevk>
domfarolino: and getComputedStyle is an obvious one we can
13:47
<domfarolino>
annevk: Ok sounds good
14:46
<domfarolino>
annevk: Also you mentioned "What requires it to be loaded eventualy?"
14:46
<domfarolino>
I guess it is a tad racy right?
14:47
<domfarolino>
Ideally it would be loaded by the three seconds in, but there's no guarantee :(
17:24
<bradleymeck>
is there something like URL.createObjectURL that lets me "reserve" a URL, but that I don't have the body for yet (without using a ServiceWorker)
17:30
<wanderview>
bradleymeck: I don't think so... but I would like to see us be able to use Response or ReadableStream in places that take a url string... like `img.srcobj = new Response(stream)`
17:31
<bradleymeck>
wanderview: I need a string URL for my use case
17:31
<bradleymeck>
which is trying to instrument ESM using browser APIs
17:32
<bradleymeck>
ESM can have circular dependencies which createObjectURL can't create
17:34
<jgraham>
bradleymeck: I assume ESM is not the European Stability Mechanism or Ejection Systolic Murmur, but I have no idea what else it might be
17:34
<bradleymeck>
EcmaScript Modules
17:36
<gsnedders>
can we write a glossary somewhere? probably not the wiki given it's so flaky…
17:56
<bradleymeck>
basically I want to be able to generate `my-url` => `import "my-url"` somehow, but can't figure out how to make the body w/ the circular reference to a URL coming out of `URL.createObjectURL`
18:39
<Domenic>
annevk has some reasons why object URLs in general are a bad design and might want to talk to you about alternatives for your use case, I dunno. E.g. have you investigated data: URLs
18:40
<bradleymeck>
Domenic: data: URLs would place same text modules in the same slot of the module map
18:40
<Domenic>
Yes, I'd hope so
18:40
<bradleymeck>
which is not workable
20:38
<jimklo>
I've got a question regarding the TextTrack.activeCues. Is there an immutable way to get the activeCues? I'm having a problem in that I cannot seem to process the cues fast enough such that I'm dropping cues that I should have handled. For ref: https://html.spec.whatwg.org/multipage/media.html#dom-texttrack-activecues