On 06/18/2014 08:06 PM, Greg Weng wrote:
> In this way the app can launch in secure pages, and it would work for
> activities, too. The app can also listen to the locking state change
> to decide whether it needs to do something to change the UI.
> Furthermore, we can finally get rid of the tricky secure Camera from
> LockScreen, which bothers us a long while (remembered the nasty,
> duplicated camera.js in System app?)
Don't we want the gecko side to take care of only launching appropriate
activities and apps when in locked mode?
This would mean that:
- the activity list in the activity picker would only include
'safeWhileLocked' activities.
- app.launch() would fail in locked mode if the launch path is not part
of the safeLockedPages.
Fabrice
--
Fabrice Desré
b2g team
Mozilla Corporation
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
