Xidorn Quan

I discussed with @annevk on IRC today about the usecase here, and we agree that it seems reasonable to add a `fullscreen` attribute to `` and/or add a `fullscreen` parameter...

> It could be equivlant to requesting fullscreen on the `body` element of the new page, so it doesn't have to be a new primitive. It couldn't. When a new...

Right. And yes, the new page can't opt-out, because its opener ask it to be in fullscreen. It can, though, exit fullscreen when it wants. Likewise, window opened by `window.open`...

Error page would be an issue, but page not designed for fullscreen would not be broken. It would just be shown as if you enter fullscreen mode.

See the [UA stylesheet](https://fullscreen.spec.whatwg.org/#user-agent-level-style-sheet-defaults) required by the spec. No additional style should be applied to the fullscreen element if it is the root element.

I'm not quite sure whether all platforms have provided API for window-level pointer restriction. It may need some investigation into whether it is implementable in general. On the permission side,...

Another thing may worth thinking about is what should happen for user-initiated focus change, e.g. when user uses Alt-Tab to switch to other window. I believe we want to untrap...

Yeah, I see that's for ``. But I don't understand why `` needs that setup. As I mentioned above, top layer should be rendered on top of the scrollbar, which...

I'm confused about the interaction between the scrollbar of the page and the top layer. So if there is a page with scrollbars, how should top layer elements be rendered?...

> what happens if the viewport is too small to fit the or fullscreened element? You cannot do anything for fullscreened element, because they are `fixed` anyway.