Bug 1432856 Comment 13 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

> IIUC, the problem we want to solve is that, the security UI should not be
> blocked by anything when we show it. In that sense, I think we can solve it
> in an easier way:
> * when we about to show the security UI, we check that we do have the focus,
> if not, kick the document out from fullscreen, and
> * when the notification is on screen, if we lose the focus, kick the
> document out from fullscreen.

I've done some testing and also implemented this behaviour by listening for the `blur` event. However this can interfere with normal usage. For example, opening a Video in fullscreen and then doing something on a secondary monitor would cause the browser to leave fullscreen.

Perhaps we do the following, but only while the fullscreen warning is shown:
1. Leaving fullscreen on `window.open()`
2. Leaving fullscreen on `window.focus()`
> IIUC, the problem we want to solve is that, the security UI should not be
> blocked by anything when we show it. In that sense, I think we can solve it
> in an easier way:
> * when we about to show the security UI, we check that we do have the focus,
> if not, kick the document out from fullscreen, and
> * when the notification is on screen, if we lose the focus, kick the
> document out from fullscreen.

I've done some testing and also implemented this behaviour by listening for the `blur` event. However this can interfere with normal usage. For example, opening a Video in fullscreen and then doing something on a secondary monitor would cause the browser to leave fullscreen.

I think the approach Chromium uses, to leave fullscreen on `window.open()` and also on `window.focus()` might be a good solution. Alternatively we could only behave this way while the fullscreen warning is shown.

Back to Bug 1432856 Comment 13