Philip Jägenstedt

What does it mean to render something on top of the scrollbar, and what happens if the viewport is too small to fit the `` or fullscreened element?

Hmm, OK. Indeed it seems weird to render scrollbars if you cannot actually scroll. Have you tested which browsers currently do this?

This is a problem in https://bugs.chromium.org/p/chromium/issues/detail?id=543946 Before trying to figure out how to make `` and Fullscreen work together, do we all agree that for Fullscreen it would make the...

> The wording could probably be: when the fullscreen element is neither null nor the root element, the computed value of viewport's `overflow` property is ignored, and `hidden` is used...

Can you confirm that the `document.hidden` attribute actually true false for background windows? I assumed that would require involving the window manager some how, and that as actually implemented it...

Is the example in https://github.com/whatwg/fullscreen/issues/58#issuecomment-250416978 the only thing that this is supposed to prevent? In my testing, the newly opened window is not hidden, which I think matches your testing....

Can you test if `document.activeElement` becomes null in non-active windows, and if there are any events fired? Given http://stackoverflow.com/questions/1060008/is-there-a-way-to-detect-if-a-browser-window-is-not-currently-active I wouldn't be surprised if there's no web exposed API to...

Ping @upsuper

> So should we allow a foreground document to put a background document into fullscreen? Given that window cannot raise itself in general, I don't see how allowing that could...

@michaelwasserman can you say a bit more about the `[[targetScreenFullscreen]]` slot? Is this about allowing a longer time to pass between use activation and entering fullscreen, or is it needed...