Updates:
Status: Untriaged
Comment #7 on issue 16735 by [email protected]: HTML 5 Video Full
screen - Feature Enhancement Request
http://code.google.com/p/chromium/issues/detail?id=16735
I gave Full Screen implementation some thought, and there are 3 parts to
it, for just
basic functionality.
1. context menu and/or hotkey. We're adding context menu for other things,
which is
turning out to be fairly hard, but it will happen.
2. make chrome go full screen. The F11 key does this.
3. render the video overtop of the entire browser.
Theres lots of little issues after that, but ignoring that, #3 is the trick
The good thing is that performance shouldnt be a problem... we have a
really fast
scaler.
We can't do it as easily as other browsers, because Chrome doesnt let us
call
functions or access the display.
a. it may be possible to ignore the region we're supposed to render, and do
the full
window. This is easy to try, but at best, wont work well.
b. we could open a new webpage. Like when you type into the omnibox a url
to an mp4,
it creates a little html page. Its fairly easy to test, by creating some
html and
pressing f11, and see how it would look. Its less clear how to hook that
in, and
free it when the user returns to windowed mode.
We've got this at Pri-2 because its really nice to have, but not a
stop-ship. And it
would certainly lead to additional bugs or feature requests.
Re screen saver. Man do I agree on that. Very annoying to have to wiggle
the mouse
every 15 minutes. I'm not sure its within the browsers control, and for
<video> tag
we can't decern between the primary movie and miscellaneous <video> for
animations
etc. I guess in full screen we know the user doesnt want to be
interupted. it
should be entered as a separate bug report, for when using the current F11
full
screen mode, which isn't specific to <video>.
trivia: in video games, full screen video is called FMV
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
