Fail to throw an InvalidStateError exception on attempts to set currentTime
Reported by
leix1.w...@intel.com,
Aug 23 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36 Steps to reproduce the problem: 1. A depth camera is plugged into the PC 2. Access to https://01org.github.io/web-test-suite/chromium/mediacapture-depth/MediaStream-MediaElement-srcObject-manual.https.html 3. When prompted, accept to share your video stream. What is the expected behavior? Throw an InvalidStateError exception on attempts to set currentTime What went wrong? Don't throw an InvalidStateError exception on attempts to set currentTime Did this work before? N/A Does this work in other browsers? N/A Chrome version: 62.0.3192.0 Channel: canary OS Version: 10 Flash Version: Shockwave Flash 26.0 r0 This issue also exists on Linux Chrome 62.0.3188.2 and Chrome OS 62.0.3190.0.
,
Aug 23 2017
Also, I believe the test might be obsolete. I can't find any reference in the spec (https://html.spec.whatwg.org/multipage/media.html#media-elements) that currentTime should throw InvalidStateError on setting under any circumstance. I do see this exception in older versions of the spec (e.g., https://dev.w3.org/html5/spec-preview/media-elements.html from 2012). foolip@: WDYT?
,
Aug 24 2017
This currentTime test refers to the spec: https://w3c.github.io/mediacapture-main/: The value is the current stream position, in seconds. On any attempt to set this attribute, the User Agent must throw an InvalidStateError exception. Is this a Chrome bug?
,
Aug 24 2017
leix1.wang@: Then it's a Chrome bug.
,
Sep 5 2017
This is defined by https://html.spec.whatwg.org/multipage/media.html#dom-media-currenttime-2 and per spec should never throw. Before https://github.com/whatwg/html/pull/1225 it would throw when there was a MediaController, but there has never been an exception specific to cameras. https://w3c.github.io/mediacapture-main/ does say "On any attempt to set this attribute, the User Agent must throw an InvalidStateError exception." Does any implementation do this? FWIW, something like this should be in the HTML spec, since it's otherwise impossible to discover the behavior by starting at the API itself.
,
Jun 21 2018
,
Jun 27 2018
The Web Platform Test that checks for this is: third_party/WebKit/LayoutTests/external/wpt/mediacapture-streams/MediaStream-MediaElement-srcObject.https.html
,
Oct 24
The spec has corrected to say that trying to set currentTime should be ignored. Since this is Chrome's behavior there is nothing to fix here. |
||||
►
Sign in to add a comment |
||||
Comment 1 by guidou@chromium.org
, Aug 23 2017Owner: guidou@chromium.org
Status: Assigned (was: Unconfirmed)