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

For `mode` specifically, it's quite likely to have a lot of overlap with the other values, e.g. a `destination` of `document` or `nested-document` should always send `mode=navigate`, whereas subresource loads with a non-empty destination will have a mode of either `no-cors` or `same-origin`. Because of this, I'd expect it to result in only a small multiplier on the number of permutations we see; but I recognize that this would not be very future-proof, especially if we decided to expose other properties of the `Request` object (which AFAIK we don't, but who knows...)

Given that there don't seem to be extremely strong opinions for either approach  -- except for the universal dislike of the bitfield -- my guess is that we should let @mikewest make the call and then blame everything on him once things inevitably blow up ;-)



-- 
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-439738703