On Tue, Jul 1, 2014 at 4:20 PM, Boris Zbarsky <bzbar...@mit.edu> wrote:
> I assume it will be the responsibility of whoever invokes a fetch to > specify a context? > Yes. > What is the process of getting new contexts added as new features are > added to the platform? > So far, I've been pinging Anne while working through the Mixed Content and CSP specs. Not sure if that's scalable. :) So, "popup". <snip> Basically, why is this a useful request context value? I think the reason it's there is that we were exploring adding auxiliary browsing context whitelisting to CSP, similar to what we do for frames. We were calling them "popups" at the time, but you're entirely correct to say that tabs would fall into the same category. It's not clear to me whether we are going to add this functionality to CSP, nor is it clear that a context is the right way of managing it. Off the top of my head, we could set an `opener` flag on fetch, distinct from `client`. If the context is "top-level" or "main frame" or whatever we call it, and there's a `client`/`opener` mismatch, we could deal with it appropriately. -- Mike West <mk...@google.com> Google+: https://mkw.st/+, Twitter: @mikewest, Cell: +49 162 10 255 91 Google Germany GmbH, Dienerstrasse 12, 80331 München, Germany Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Geschäftsführer: Graham Law, Christine Elizabeth Flores (Sorry; I'm legally required to add this exciting detail to emails. Bleh.) _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
