<div class="gmail_quote">With the video tag and web games gaining traction, it seems like there
should be a way for apps to provide fullscreen and better control schemes
to users. Of course, spoofing and clickjacking are major concerns, but
I liked Alpha Omega's suggestion a few weeks ago [1] to specify a
"fullscreenable" attribute to certain elements that hint to the UA that
the object would be appropriate to consider for fullscreen.
Similarly, for content that uses relative mouse motion or requires great
precision (like a first-person view), it would be useful to have a
"mouselockable" attribute; upon a UA defined interaction, the mouse would be locked within the particular element and report relative mouse events until the user disengages the lock.<br>
<br>I can imagine a variety of ways browsers could expose these features:
overloading F11 to gray out all portions of page except those are
fullscreenable; pressing F11 repeatedly to cycle through elements; having a right click option on
fullscreenable elements, automatic hover borders etc. <br><div class="im">
<br>Any interest or reasons why this wouldn't work?<br><br>[1] <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-June/020479.html" target="_blank">http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-June/020479.html</a><br>
<br><br></div></div>