This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22249 - should setting media.currentTime throw InvalidStateError?
Summary: should setting media.currentTime throw InvalidStateError?
Status: RESOLVED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: Media Capture and Streams (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: public-media-capture@w3.org
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-03 15:42 UTC by Dominique Hazael-Massieux
Modified: 2013-08-27 08:55 UTC (History)
2 users (show)

See Also:

Attachments

Description Dominique Hazael-Massieux 2013-06-03 15:42:17 UTC 
The spec currently says that the UA must ignore attempts to set media.currentTime when that media is assigned a mediastream.

But the HTML spec says:
"On setting, if the media element has a current media controller, then the user agent must throw an InvalidStateError exception"
http://www.w3.org/html/wg/drafts/html/CR/embedded-content-0.html#dom-media-currenttime

and a MediaStream assignment is similar on many other aspects to having a media controller, which suggests that trying to set currentTime should throw an InvalidStateError; that's also what Firefox currently does.
Comment 1 Harald Alvestrand 2013-08-27 08:55:54 UTC 
Resolved in 20130824 version of MediaCapture.