I'm not sure what happens if a page requests full-screen currently, but probably bad things. Conceptually, implementing full screen in b2g is very easy: the b2g chrome package already owns a full-screen XUL <window>, so all full-screen means is hiding "home screen" UI like status bars etc. For now, we can communicate full-screen state changes to gaia using events fired from b2g chrome. In the future, "silent intents" might be the way to go. We need to make sure the CSS pseudo-selectors etc. are honored properly. This gets harder for content loaded in a browser app's <iframe browser>, but that work is covered by a separate bug. "Installed app" fullscreen is much higher priority.

This is patch is quite subtle and complicated, so please review carefully.

Comment on attachment 596432 [details] [diff] [review] Enable DOM full-screen API for b2g Finally a patch I am qualified to review.