Handling of some HTML media element fields is incorrect for MediaStreams |
||||
Issue descriptionpreload: it returns "metadata" by default and the attribute can be changed. According to spec, it should always return "none" and setting a value should be ignored. defaultPlaybackRate: it allows setting a value, but according to spec setting a value should be ignored and it should always return 1.0. playbackRate: it allows setting a value, but according to spec setting a value should be ignored and it should always return 1.0. currentTime: setting a value is ignored, but according to spec it should fire an InvalidStateError exception. Spec: https://w3c.github.io/mediacapture-main/#mediastreams-in-media-elements
,
Oct 4
,
Oct 4
,
Oct 4
,
Oct 10
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b118de6d6083691a177ab39bb455b624380c9e0f commit b118de6d6083691a177ab39bb455b624380c9e0f Author: Guido Urdaneta <guidou@chromium.org> Date: Wed Oct 10 23:26:53 2018 Fix media element field behavior when playing MediaStreams Set operations for the preload, defaultPlaybackRate and playbackRate fields should be ignored when the media element is playing a MediaStream. In addition, the preload field must always return "none", and defaultPlaybackRate and playbackRate must both return 1. See https://w3c.github.io/mediacapture-main/#mediastreams-in-media-elements Bug: 892114 Change-Id: Id50e557056b9501330bb753535e2cbdb80fc4667 Reviewed-on: https://chromium-review.googlesource.com/c/1261445 Commit-Queue: Guido Urdaneta <guidou@chromium.org> Reviewed-by: Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#598566} [modify] https://crrev.com/b118de6d6083691a177ab39bb455b624380c9e0f/third_party/WebKit/LayoutTests/external/wpt/mediacapture-streams/MediaStream-MediaElement-srcObject.https.html [modify] https://crrev.com/b118de6d6083691a177ab39bb455b624380c9e0f/third_party/blink/renderer/core/html/media/html_media_element.cc
,
Oct 24
The spec has been amended to specify that setting currentTime should be ignored, so no further work needed here. |
||||
►
Sign in to add a comment |
||||
Comment 1 by guidou@chromium.org
, Oct 4