GV API for site permissions
Categories
(GeckoView :: General, enhancement, P1)
Tracking
(Not tracked)
People
(Reporter: cpeterson, Unassigned)
References
Details
(Whiteboard: [gvtv] [geckoview:fenix:p1] [geckoview:fenix:m2])
We need a GV API to manage site permissions like autoplay or microphone.
Should Gecko remember the site permissions (and expose a GV API for the app to get and set permissions) or should GV always ask the app (and the app will remember the permissions)? Having the app remember the permissions might be easiest: the GV API would be simpler and the app is responsible for the permission prompt and management UI anyways.
[geckoview:fenix:p2] because I assume Fenix will want to manage site permissions.
|
Reporter | |
Comment 1•6 years ago
|
||
Site permissions are a must-have for Fenix MVP and scheduled for Fenix M2.
|
||
Comment 2•6 years ago
|
||
I think my preference would be that GV always asks. The UI mocks for Fenix have very fined-grained controls and feeding all that into GeckoView and back seems like a massive painful thing. And in Fennec it was always a bit awkward to wait for Gecko to get access to certain data. :)
|
|
Reporter | |
Comment 3•6 years ago
|
||
P1 because site permissions are a must-have for Fenix MVP.
|
||
Comment 4•6 years ago
|
||
Talking to Randall we think our Permissions Delegate API will serve this purpose and the app can keep track (store, or not) of what user has requested. Gecko will ask for permission everytime and an android component can intercept and query user or use a stored preference (per page db).
Sebastian do you agree? Do you want to close this one and use a github issue?
|
|
Reporter | |
Updated•6 years ago
|
|
|
||
Comment 5•6 years ago
|
||
(In reply to David Bolter [:davidb] (NeedInfo me for attention) from comment #4)
Talking to Randall we think our Permissions Delegate API will serve this purpose and the app can keep track (store, or not) of what user has requested. Gecko will ask for permission everytime and an android component can intercept and query user or use a stored preference (per page db).
Sebastian do you agree? Do you want to close this one and use a github issue?
Great! If this is already working this way then we shouldn't need anything more from GV.
We are tracking the work for this project here:
https://github.com/orgs/mozilla-mobile/projects/8
Description
•