Re: [w3ctag/design-reviews] `sec-metadata` (#280)

Hey, @annevk!

> I see you removed the request's initiator dependency, thanks!

I'd still like to get the "`download`" vs non-download distinction back somehow, but the remaining bits of `initiator` are much less important to me, so dropping it wasn't hard.

> `target` seems wrong for workers. I don't think we should deviate too much from https://fetch.spec.whatwg.org/#subresource-request et al.

The interesting distinction in `target` is really `top-level` vs `nested`. I would be perfectly happy dropping it entirely from non-navigational requests. One way to do that could be to split the "`document`" `destination` into "`top-level-document`" and "`nested-document`", which would allow us to drop `target` entirely.

> Instead of `destination` accepting a string, I think we should reuse fetch as a value there similar to https://fetch.spec.whatwg.org/#concept-potential-destination.

I don't quite understand: are you saying that instead of `destination=""`, you'd prefer `destination="fetch"`? That seems fine to me.

Also: I don't see "potential destination" used anywhere in Fetch. Where is it used?

> The document purports to be in the Public Domain and under copyright owned by Google.

Huh. That was dumb. I'll fix it.

> I'm a little uncomfortable sharing all this data. It seems like it could easily make #76 much worse.

What bits of data are you uncomfortable sharing? `destination`? It's also not clear to me how you see this relating to #76. Could you elaborate?

> I'm also not entirely persuaded by "H/2 compression will save us". The whole point of adding compression there was to reduce the existing bloat, not to provide a way to add more.

My point isn't that compression means that we can magically add everything ever to HTTP requests. I'm claiming that compression reduces the apparent cost of the header to something that seems pretty manageable, and (IMO) worth the tradeoff.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/280#issuecomment-394596466