22143 2013-05-22 20:05:19 +0000 MediaPlaybackQuality interface should be limited to HTMLVideoElement 2013-06-01 21:42:46 +0000 1 1 1 Unclassified HTML WG Media Source Extensions unspecified PC Windows NT RESOLVED FIXED PRE_LAST_CALL P2 normal --- 1 jdsmith acolwell acolwell cyril.concolato mike public-html-media public-html-bugzilla oldest_to_newest 88082 0 jdsmith 2013-05-22 20:05:19 +0000 Section 7.2 of the current draft adds MediaPlaybackQuality to the HTMLMediaElement. These can be audio only, in which case the frame quality metrics shouldn't apply. Recommend replacing HTMLMediaElement with HTMLVideoElement in 7.2: 7.2 New Attributes and Behavior This section specifies new attributes and internal state that are being added to the HTMLVideoElement. Each HTMLVideoElement will maintain a total video frame count variable that keeps track of the total number of frames that have been displayed and dropped. This variable is initialized to 0 when the element is created and whenever the media element load algorithm is invoked. It is incremented when a video frame is displayed or when the dropped video frame count is incremented. Each HTMLVideoElement will maintain a dropped video frame count variable that keeps track of the total number of frames that have been dropped. This variable is initialized to 0 when the element is created and whenever the media element load algorithm is invoked. It is incremented when a video frame is dropped predecode or when a frame is decoded but dropped because it missed a display deadline. partial interface HTMLVideoElement{ readonly attribute MediaPlaybackQuality playbackQuality; }; This paragraph is a subparagraph of 7. HTMLMediaElement Extensions, which makes this fit a little awkward. It fully describes the requested change though. 88145 1 acolwell 2013-05-23 18:31:00 +0000 Marking all pre-Last Call bugs 88163 2 acolwell 2013-05-24 00:17:30 +0000 HTMLMediaElement contains videoTracks which would be present on an HTMLAudioElement eventhough video tracks would not be displayed. I don't know the history of this choice, but it does set precedent for video related functionality to reside there. What is the perceived harm in having an attribute in HTMLMediaElement? This seems like a natural place to put any future playback stats we may want to expose, video specific or otherwise. If the prevailing opinion still favors placing this on HTMLVideoElement, then I'd like to propose that MediaPlaybackQuality be renamed to VideoPlaybackQuality and the attribute name be changed to videoPlaybackQuality. Dropping Playback from both names may be a good idea as well. I'm suggesting this primarily to avoid an attribute name conflict if we ever do decide to put a playbackQuality attribute on HTMLMediaElement that contains metrics suitable for all types of media elements. 88546 3 acolwell 2013-06-01 21:42:46 +0000 Changes committed https://dvcs.w3.org/hg/html-media/rev/1ac9c2205a7b