On Tue, Jul 1, 2014 at 4:20 PM, Boris Zbarsky <bzbar...@mit.edu> wrote:
> What is the process of getting new contexts added as new features are added
> to the platform?
File a bug.
> So, "popup".
>
> Is <a target="_blank" href="whatever"> a "navigation" or a "popup"? What
> about <a target="something" href="whatever">? Does it depend on whether an
> existing navigation context with the name "something" exists? What about
> window.open("whatever", "something")? What about <form action="whatever"
> target="_blank">? Is there a difference between navigations to _blank
> target that will be show in new windows vs new tabs?
>
> Basically, why is this a useful request context value?
Good question. From what I remember the main motivation was having
something distinct from navigating the top-level browsing context. A
service worker might want to know whether it's "app" top-level
browsing context is being navigated or whether it's an auxiliary
browsing context.
> As long as we're here, is the associated origin of a request related to the
> request context or the response? It would be good to make that clear.
A request's origin is set by the API that initiates the fetch. A
response does not really carry an origin.
> Should the default mode be no CORS or CORS? It might make some sense to
> have it be CORS... Similar for response tainting.
Yeah maybe. (The response tainting default value is not really of any
concern. As the note points out it is a bookkeeping detail and not
actually part of the spec-facing API.)
--
http://annevankesteren.nl/
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
