Marijn Kruisselbrink

Heh, yeah. I think earlier on we had some thoughts that the via the WritableStreamDefaultWriter should only accept bytes, and we'd provide the Stream.write as a convenience to support blobs...

I suppose it applies to anything that needs to load the entire resource in memory or store it on disk. Not sure if anything other than XHR has progress events...

> The `img` element has `progress` events in its specification. That's what I get for trusting stack overflow rather than reading the actual spec... Yeah, in that case that seems...

https://www.chromestatus.com/metrics/feature/timeline/popularity/9 is another really odd one as a use counter with supposedly extremely high usage (>50%), that doesn't exist and hasn't existed in the code base for a very long...

Why wouldn't other UAs be able to use the Origin-Trial header/http-equiv? Our implementation just ignores any tokens that aren't signed by our keys/that aren't in our format. It's always been...

That's a bug in the (lack of) spec. I started trying to more formally specify the actual format of any of this, but that work seems to have mostly gotten...

Getting more and more off topic for this issue, but in addition to specifying a minimum tag size browsers should support, do we also want to specify a minimum number...

I thought about somehow trying to reference `navigator.onLine` here, but ended up not doing so since its definition is inside section 7.7, which has the scary "This feature is in...

Yes, this is described in https://slightlyoff.github.io/BackgroundSync/spec/#history-leaking.

and the other paragraph in the privacy considerations section of course. It definitely is a potential problem, but not sure if there is much we can do about it.