On Mon, 8 Jan 2018, at 20:34, Avi Drissman wrote:
> *Contact emails*
>
a...@chromium.org
>
> *Spec*
>
https://fullscreen.spec.whatwg.org/
>
> *Summary*
> If a page calls |window.focus()| on a popup, it is exited from fullscreen.
>
> *Motivation*
> Fullscreen and window focusing do not mix well. Window focusing can
> interfere with the signals that Chromium uses to tell the user that they
> are in fullscreen (for those with security privileges, see
>
https://crbug.com/776418).
>
> HTML5 fullscreen is an immersive experience with one window taking over the
> entire screen. window.focus() is a request to change the focused window.
> Because they have different goals (immersion vs multi-window operation),
> this intervention should not affect legitimate sites.
>
> We currently exit fullscreen for JavaScript dialogs
> <
https://www.chromestatus.com/feature/5669548871122944> and we currently
> exit fullscreen for popups (this behavior is so old it predates
>
chromestatus.com). This intent is a follow-up to those features.
An obvious alternative would be to ignore the `focus()` call. Do we prefer to instead exit fullscreen for consistency with the dialog/popups behaviour?
> *Compatibility risk*
> Low. As described, because these two features have two different goals,
> legitimate sites should not be affected.
I guess there will be use counters to check this?
> *Will this feature be supported on all six Blink platforms (Windows, Mac,
> Linux, Chrome OS, Android, and Android WebView)?*
> No, fullscreen is a desktop-only feature.
Android and WebView have fullscreen support.
-- Mounir