(This relates to the question I asked yesterday about whether the embedding
API for Crosswalk does anything with the permissions field when running on
Android.)
I've been having a close look at the permissions field in the manifest, and
how it's managed by make_apk.py.
This mapping table is what I'm working from:
permission_mapping_table = {
'contacts': ['android.permission.READ_CONTACTS',
'android.permission.WRITE_CONTACTS'],
'geolocation': ['android.permission.ACCESS_FINE_LOCATION'],
'messaging': ['android.permission.READ_SMS',
'android.permission.READ_PHONE_STATE',
'android.permission.RECEIVE_SMS',
'android.permission.SEND_SMS',
'android.permission.WRITE_SMS'],
'devicecapabilities': [],
'fullscreen': [],
'presentation': [],
'rawsockets': [],
'screenorientation': [],
'vibration': ['android.permission.VIBRATE']
}
Some of the fields are used to set <uses-permission> elements in
AndroidManifest.xml.
Some of the entries don't affect packaging (presentation, fullscreen,
rawsockets, screenorientation etc.). Do they instead affect the application
when the manifest is loaded (e.g. if you use loadAppFromManifest())?
And will a feature be disabled unless the permission is specified (so you
have to enable fullscreen explicitly, for example)? Or does specifying this
permission just prevent the user from getting a "grant permission?" popup
when these APIs are accessed?
Finally, is there a mechanism in the embedding API to set a permission
without specifying it in a manifest.json file? (I can't see one.)
Thanks.
Elliot
--
Elliot Smith
Senior Software Engineer
Intel Open Source Technology Centre
_______________________________________________
Crosswalk-help mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
