(See attached screenshot) Sometimes we first request a runtime permission and then ask the user whether the website is allowed to do something with it (Camera, Microphone). And other times we ask first if the website can use some feature and then request the system permission (Location). The current approach has technical reasons. For example sometimes we need the system permission earlier to show some information in the prompt (e.g. number of camera devices). Ideally we'd show a prompt for the website first and only if this has been accepted we request a system permission. And preferably we already let the user know that a system permission will be needed. But then we might still need to ask what devices (camera) the user wants to share with the website. So to sum this up: To do this right we need to completely rethink this flow.
To be more integrated with the system, could we potentially skip the doorhanger stage? I.e. user presses button > system prompt shows up Though, messaging could be weird because it would always seem like Fennec is asking for the permissions. Sebastian, what's the downside to forcing a specific order in this flow? E.g. if we wanted to always start with a doorhanger, then a system prompt.
(In reply to Anthony Lam (:antlam) from comment #1) > To be more integrated with the system, could we potentially skip the > doorhanger stage? I.e. user presses button > system prompt shows up This would only work for cases where the user has not granted the permission. After the permission has been granted we'd still need to show the doorhanger for other website visits. Or do you want this flow only for a (first) visit without system permission? Some doorhanger have additional controls (e.g. select which camera) so we couldn't get completely rid of it. > Sebastian, what's the downside to forcing a specific order in this flow? > E.g. if we wanted to always start with a doorhanger, then a system prompt. Some information we show in the doorhanger (See camera screenshots) needs information we can only obtain after the app has the system permission.
You need to log in before you can comment on or make changes to this bug.