In the Comms Area we are envisaging two scenarios on which we will need to be able to embed an app (in an iframe) from another app. A/ Dialer embedding the Contacts App, being Contacts and Dialer independent apps, thus removing the entry points hack B/ Contacts being able to instantiate importers in <iframes> being the importers separate apps from Contacts. The suggestion would be to have a new permission: "embed-apps": { manifestURLs: ['app://contacts.gaiamobile.org'] }

Speaking specifically about A/ from comment 0. Why couldn't the dialer app render a contacts list itself? Opening a separate app in an iframe means spawning a new process which both takes a long time, and uses a lot of memory. Is this just to enable rendering facebook contacts? If so I think we can likely find a solution which allows the dialer to access the facebook contacts through a DataStore, without exposing it to other apps.

(In reply to Jonas Sicking (:sicking) from comment #1) > Speaking specifically about A/ from comment 0. > > Why couldn't the dialer app render a contacts list itself? Opening a > separate app in an iframe means spawning a new process which both takes a > long time, and uses a lot of memory. Because, the requirement in the past was to open the contacts app embedded on dialer, not rendering contacts. > > Is this just to enable rendering facebook contacts? If so I think we can > likely find a solution which allows the dialer to access the facebook > contacts through a DataStore, without exposing it to other apps. No, that's not for Facebook. The dialer already has access to FB contacts through datastore