On Thu, Aug 14, 2014 at 6:16 AM, Ben Francis <[email protected]> wrote: > On Wed, Aug 13, 2014 at 11:19 PM, Jonas Sicking <[email protected]> wrote: >> >> How will scopes solve that? Say that App A navigates to URL X which is >> not in A's "scope", but is in A's "open-in-app", then X will be loaded >> within A. >> >> The user then goes to app B which also navigates to X, and X is not in >> B's "scope", but is in B's "open-in-app". >> >> Finally the user opens pulls down the rocketbar and types the X URL. >> Do we now open X in A, in B or in the system browser? > > I would say that URL X is still not in the "scope" of any app so in the case > of being manually entered into the Rocketbar it should open in a browser > window, regardless of what app(s) it has previously been opened in. > >> Another edge case is if the user brings up the rocketbar, which >> contains the current URL of the current page, and that page is outside >> of "scope", but inside of "open-in-app" of the current page, and then >> simply presses "enter". Does that reload the current page within the >> current app. Or does it switch to the browser app. > > That is a good question. I would say it also opens a browser window, but > that may feel a little strange in practice. Currently we don't display URLs > in the Rocketbar for hosted apps so that isn't a problem. > > > Another question which was brought up in bug 996039 was how application > scope should work for packaged apps.
Once we implement the "http://foo.com/package.zip!//file.html"; URLs for packaged apps, it should work just like for hosted apps. The only thing that's special is that we should somehow default the scope for a packaged app to be just the package itself. Not the whole package's origin. / Jonas _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
