Cross-domain links in <iframe mozapp> should open in the browser app. This is what we do for desktop webapps, bug 707836. Presumably we need web intents before we can do this. Also, I'm pretty sad we have to re-implement this sort of thing for b2g.

Can't we use the usual nsBrowserAccess mechanism?

All cross-domain links? Or can we have this behaviour for anchors specified with target="_blank"?

(In reply to Chris Van Wiemeersch [:cvan] from comment #2) > All cross-domain links? Or can we have this behaviour for anchors specified > with target="_blank"? All cross-domain links. An app cannot move to another domain. > Can't we use the usual nsBrowserAccess mechanism? That's tagged off the browserDOMWindow? Maybe... We really should use intents here.

(In reply to Justin Lebar [:jlebar] from comment #3) > (In reply to Chris Van Wiemeersch [:cvan] from comment #2) > > All cross-domain links? Or can we have this behaviour for anchors specified > > with target="_blank"? > > All cross-domain links. An app cannot move to another domain. That's not consistent behavior with desktop, possibly with Android as well, although the Android piece is up to debate. We should strive for consistency here in this area especially, otherwise, we'll end up confusing developers to implement apps in different ways for different platforms (especially important that the Android piece = B2G piece). Why not follow the target blank specification in bug 752666 in desktop? References: * Desktop equivalent bug - bug 752666 * Android equivalent bug - bug 766802

> All cross-domain links. An app cannot move to another domain Jonas tells me I misunderstood the implications of bug 752666. We should match the behavior on desktop.

On desktop we open all target=blank links in the browser, whether or not they are cross-domain.

This will be fixed on the Gecko side by bug 769254. Gaia will still need to figure out its "open the browser" magic.

+ing dupe