- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Mon, 21 Jun 2010 12:34:57 +1000
On Mon, Jun 21, 2010 at 12:07 PM, Nils Dagsson Moskopp <nils-dagsson-moskopp at dieweltistgarnichtso.net> wrote: >> >> There is also the issue of the context menu not being an especially >> intuitive or discoverable way of activating it, especially if all the >> rest of the controls are buttons below the video. > > If this is the only problem, it clearly is an an implementor issue. > UAs could show a little fullscreen button besides the volume / mute > controls, no extra markup attribute needed. Not quite. Every functionality in the @controls this far has an analogous javascript function so that Web page authors that cannot activate the @controls and have to run their own (e.g. for corporate design issues) have the functionality to replace the buttons with a custom button. This would be required with a fullscreen button as part of the @controls, too. Honestly, is security with fullscreen really such a big issue that we absolutely cannot afford to have a javascript control for it? Cheers, Silvia.
Received on Sunday, 20 June 2010 19:34:57 UTC