This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html Multipage: http://www.whatwg.org/C#media-controllers Complete: http://www.whatwg.org/c#media-controllers Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: restrained media controller should not depend on blocked media elements Posted from: 83.218.67.123 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 OPR/21.0.1432.39 (Edition Next)
I implemented the activation behavior (click to play/pause) for media elements and used the same logic internally to toggle paused state from the native controls. This revealed an oddity in the definition of a restrained media controller. If the media controller is playing and its slaved media elements are paused (their initial states), the controller is usually restricted and the UI would show a play button. However, when seeking, the media element's readyState will fall down to HAVE_METADATA momentarily, causing it to be blocked, so that the controller is then not restricted (nor paused) so a pause button would be shown instead. The net result is that when dragging the seek bar of a paused media element attached to a playing media controller, the play/pause button will flicker between the two states. Of course I could just fix the controls to hide the issue, but I don't see why a blocked media element is part of the definition of restricted. In general it would make sense if a single media element slaved to a media controller behaved like a standalone media element, and there readyState is simply not involved in determining whether clicking should play or pause.
FWIW, I've tested simply removing the bit about blocked media elements from the implementation and that fixes the flickering problem.
Yeah I dunno what I was thinking there.
Checked in as WHATWG revision r8585. Check-in comment: restrained media controller should not stop being restrainted just because the video elements haven't finished loading their content http://html5.org/tools/web-apps-tracker?from=8584&to=8585
Thanks!