25429 2014-04-23 14:57:56 +0000 restrained media controller should not depend on blocked media elements 2014-04-30 09:32:02 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#media-controllers P3 normal Unsorted 1 contributor ian ian mike philipj contributor oldest_to_newest 104275 0 contributor 2014-04-23 14:57:56 +0000 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) 104277 1 philipj 2014-04-23 15:10:44 +0000 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. 104279 2 philipj 2014-04-23 15:19:17 +0000 FWIW, I've tested simply removing the bit about blocked media elements from the implementation and that fixes the flickering problem. 104642 3 ian 2014-04-29 00:18:18 +0000 Yeah I dunno what I was thinking there. 104643 4 contributor 2014-04-29 00:18:29 +0000 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 104795 5 philipj 2014-04-30 09:32:02 +0000 Thanks!