開啟 2014年8月5日 at 下午12:40:15, Fabrice Desré (fabr...@mozilla.com) 寫:
Privileged packaged apps can specify their origin in the manifest (so
you can get app://my-app as origin).
A dump question,
Is it marketplace’s responsibility to make sure the ‘my-app’ is unique and has
certain mapping to real web site origin?
For example, could I use |mozilla.com| as origin in my private app?
--
Alive C. Kuo, Firefox OS, Senior Software Engineer at Mozilla Taiwan, Taipei
office.
Do we want to let another app to claim these origins as open-in-app?
Fabrice
On 08/04/2014 08:55 PM, Jonas Sicking wrote:
> On Mon, Aug 4, 2014 at 8:06 PM, John Hu <j...@mozilla.com> wrote:
>> Hi Jonas,
>>
>> How about packaged app? If they are pre-installed app, we may know their URL
>> to fill in "scope" and "open-in-app". But if they are downloaded from
>> marketplace, the URL of them are all UUIDs.
>
> I think the main use case for "scope" for a packaged app is going to
> be to declare that the "scope" is all URLs inside the package. That
> can be done by simply doing
>
> {
> ...
> "scope": "/*"
> }
>
> Or by simply leaving out the scope entirely, since it defaults to the
> origin of the manifest, which is the app://uuid/.
>
> As things stand right now a packaged app could enumerate any normal
> http website as part of "open-in-app". But they couldn't enumerate
> other packaged apps since you couldn't know the URL of the other
> packaged apps on the user's device.
>
> However once we implement the changes that I described in the "Future
> of packaged apps" thread, this changes a lot.
>
> How exactly remains to be seen I think since there's still some
> details there to figure out.
>
> / Jonas
>
--
Fabrice Desré
b2g team
Mozilla Corporation
_______________________________________________
dev-webapi mailing list
dev-web...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-webapi
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
