Xidorn Quan

The issue is that, we may also need that in the removing steps. If we replace step 3 with `body.removeChild(fa)`, should the inner document exit fullscreen? Maybe that could happen...

Yeah, it worked before, because iframe if any may only be the top in the fullscreen element stack. I think those steps should be moved to **unfullscreen node** because descendent...

Ahh... you're right... Then they are two different issues...

I agree with the third. We should not trigger resize if we are already in fullscreen. The first is only simple in concept. I think that would require impls to...

Currently Edge and Safari allow user to enter fullscreen regardless of whether it is allowed by DOM. Firefox is... something in-between, which doesn't make much sense. We want to align...

I would probably be against allowing `requestFullscreen()` inside `DOMContentLoaded` or `load`, because timing of those events can be controlled by websites. I think the purpose of the current mitigations is...

That would probably make it pretty unreliable. In some network environment, time between `navigationStart` and `responseStart` could be seconds, right? Also navigation could be triggered by script as well. This...

If what you want is that, when user clicks your link anywhere, the page opens in fullscreen directly, I would pretty much be against this idea. I don't believe user...

> Allowing any page to go fullscreen on initial load is more than would be required to solve the use case @duanyao describes I think. It's simpler than other solutions...

> With current fullscreen spec and implementation, a page can already enter fullscreen somewhat unexpectedly -- click on an arbitrary point on a page can trigger fullscreen. My suggestion still...