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 22247 - Setting loop attribute on a media element reading from a MediaStream
Summary: Setting loop attribute on a media element reading from a MediaStream
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:08 UTC by Dominique Hazael-Massieux
Modified: 2014-02-12 08:41 UTC (History)
2 users (show)

See Also:

Attachments

Description Dominique Hazael-Massieux 2013-06-03 15:08:59 UTC 
Currently, the spec says that the only valid value for media.loop when the media reads from a MediaStream is "false"; but it's not clear whether it means that setting it to true doesn't change the value of the attribute, or merely that it doesn't have any effect.

I'm not finding any clear guidance on this from the HTML spec:
http://www.w3.org/html/wg/drafts/html/CR/embedded-content-0.html#attr-media-loop

Currently, Firefox accepts to set it to true, but I don't know if that's intended or just the current state of implementation.
Comment 1 Dominique Hazael-Massieux 2013-06-03 15:13:01 UTC 
The same applies to media.preload
Comment 2 Adam Bergkvist 2013-10-08 12:04:11 UTC 
My interpretation is that it's ok to set it and the value will change, but it has no effect.
Comment 4 Adam Bergkvist 2013-10-17 11:33:36 UTC 
Fixed in Editor's draft v20131017
Comment 5 Dominique Hazael-Massieux 2014-02-12 08:41:36 UTC 
my comment also applied to .preload — I think the spec should have the same treatment for preload as it has for loop (i.e. any value is acceptable, but won't have any effect)