Currently missing video behaviors: - When autoplay is off, a play button should display in the center of the video and the entire content area should be a clickable play button. The video should fade partially to black. - While the video is playing, the content area should be a clickable pause button. Clicking it to pause should produce the same play button as above, and the video should fade similarly to black. The reason for adopting this already widely-used video interaction is that the clickable area for the most common two tasks - play and pause - is as large as possible and therefore faster and easier to click. It also means that if the video is autoplaying and the user does not want it to play, they don't need to hover over the video and wait for the UI pause/play button to appear. This should work the same in fullscreen mode as standard play mode.

This doesn't seem like something we'd take on branch for 1.9.2.

One issue need to be considered:- If the web developer is not using VIDEO tag just as normal player, but something other then that, this feature will be a trouble to him. example at http://www.double.co.nz/video_test/video.svg you can click and drug the video. Here we dont want the pause and play action when user click it to drag. One option, this feature should available only when controls are enabled.

Yes, this should definitely only happen when controls are enabled!

This bug has been broken up into two bugs. This bug will stay as the bug for making the video content area a large play/pause button, while bug 666306 is now the bug for making the video initially show a large play button if autoplay is off.

The video content area is now clickable to play/pause the video.

I forgot to add that the patch for this bug only enables this ability if the video controls are visible.

Comment on attachment 541120 [details] [diff] [review] Patch for bug 518008 Review of attachment 541120 [details] [diff] [review]: ----------------------------------------------------------------- I'm not a toolkit peer.

Based on our conversation offline, I have changed the button back to a spacer and am now using the click handler. This works just as well and will probably not introduce any weird a11y issues.

Bah, I typed my comment for our conversation in a tab but never saved it: From a quick chat: It's probably lightly better to just add a onclick handler to the spacer, instead of making it a <button>. It's kind of a weird case where we literally are not interested in anything other than the click (and so have to do extra stuff to make the button invisible). The slight difference that made onclick win out for me is that for A11Y we actually don't want the button showing up at all. It's redundant with the existing play/pause button (which is accessible), and would probably just be annoying to show up as a separate thing anyway.

Comment on attachment 541422 [details] [diff] [review] Patch for bug 518008 - version 2 I hate to bikeshed, but I think I'd rather keep it named controlsSpacer. r+ with that simple rename!

Changed the name of the spacer back to controlsSpacer.

:Dolske, with the above rename, can you land this for me?

Comment on attachment 541872 [details] [diff] [review] Patch for bug 518008 - version 3 No re-review needed, but r+ anyway. :) I'll just flag this checkin-needed lest I not get to it this weekend.

A little problem, rightclick will trigger it as well, normally you rightclick because you want to see the context menu other than play/pause it.

(In reply to comment #17) > A little problem, rightclick will trigger it as well, normally you > rightclick because you want to see the context menu other than play/pause it. Thanks for catching that. I have logged bug 667323 for this issue.

Using the steps from the description and a youtube video it's enough to verify this bug? Thanks

(In reply to Vlad [QA] from comment #19) > Using the steps from the description and a youtube video it's enough to > verify this bug? > Thanks This bug only applies to HTML5 <video> when controls are enabled, therefore youtube videos will not apply.

I've verify this on o youtube video with html5 enabled. If I right-click on the video, in the context menu I have "About html5" so I guess it ok. The whole video acts like a play/pause button. It's enough to verify this? thanks

Back again :) I've now tested this bug on this test page: http://dolske.net/mozilla/tests/video/tests.html# Everything is working as expected. Setting resolution to Verified Fixed on Mozilla/5.0 (Windows NT 6.1; rv:7.0) Gecko/20100101 Firefox/7.0 beta 3

This really should be left to end developers to implement in JavaScript. See: https://bugzilla.mozilla.org/show_bug.cgi?id=693014