- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Mon, 23 Aug 2010 17:11:43 +1200
On Mon, Aug 23, 2010 at 5:03 PM, Adam Barth <w3c at adambarth.com> wrote: > On Sun, Aug 22, 2010 at 9:56 PM, Robert O'Callahan <robert at ocallahan.org> > wrote: > > On Mon, Aug 23, 2010 at 4:42 PM, Adam Barth <w3c at adambarth.com> wrote: > >> Oh, I think the iframe-at-a-time is an easier model to work with since > >> the scripting context will get adopted into the full-screen view > >> together with the elements. > > > > It requires the author to put each part of their page that they want to > go > > fullscreen into its own subframe. That is cumbersome. With my proposal, > most > > existing pages and player UIs would work if you just call > > "element.requestFullScreen()" in some event handler. > > But it doesn't go full screen, right? Didn't you say above that the > location bar is still there? > That depends on the UA. Assuming we implement this API using our existing fullscreen functionality, in Firefox the element would be fullscreen, but if the user moves the mouse to the very top of the screen some browser chrome will pop down temporarily, including the URL bar. Rob -- "Now the Bereans were of more noble character than the Thessalonians, for they received the message with great eagerness and examined the Scriptures every day to see if what Paul said was true." [Acts 17:11] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100823/033d5925/attachment.htm>
Received on Sunday, 22 August 2010 22:11:43 UTC