The problem we see is: in the case of the HTML attachment provided, the webpage asks for fullscreen and *then* requests the Microphone permission. So, at the time our code processes the Fullscreen request, we have no way to know that there's a Microphone permission request coming. An option might be to have a kind of time threshold where we wait some defined amount of time (*x seconds) before going fullscreen, so that we can process permission requests in that time. But we think that the issue would still exist, the website would only have to wait for *x seconds* before requesting the permission. (Unless we show a kind of warning that you're about to go fullscreen before really going fullscreen). Another option would be to show the Fullscreen notification somewhere else on the screen, so that we make sure it's visible. Is there something we are missing? Does someone have an opinion on how to correctly handle this case?
Bug 1871217 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The problem we see is: in the case of the HTML attachment provided, the webpage asks for fullscreen and *then* requests the Microphone permission. So, at the time our code processes the Fullscreen request, we have no way to know that there's a Microphone permission request coming. An option might be to have a kind of time threshold where we wait some defined amount of time (*x seconds*) before going fullscreen, so that we can process permission requests in that time. But we think that the issue would still exist, the website would only have to wait for *x seconds* before requesting the permission. (Unless we show a kind of warning that you're about to go fullscreen before really going fullscreen). Another option would be to show the Fullscreen notification somewhere else on the screen, so that we make sure it's visible. Is there something we are missing? Does someone have an opinion on how to correctly handle this case?