Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36)

The iframe solution is not harder to write than `<a allowfullscreen>`, but they are *different* in many aspects, and my conclusion is that it is usually not always a viable alternative.

* iframe is hard to bookmark.
* iframe impacts the layout of the embedding page (takes much more screen real estate than `<a>`). UI designer of the embedding page may feel unconformable with this.
* Embedding page is coupled with the embedded page. For example, the size of the iframe has to be specified by the embedding page, which means the size of the embedded page can't be changed easily in future.
* iframe is a larger attack surface than link. Many sites may forbid or filter iframe in user generated content, but I guess `<a allowfullscreen>` is much less a concern.
* iframe consumes much more RAM than `<a>`, especially for complicated pages like presentations. A page may not afford to embed multiple of them.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/issues/36#issuecomment-248191980