8736 2010-01-14 11:05:49 +0000 Decision to playback for media should be left to the user agent 2011-03-08 16:17:32 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC Windows NT VERIFIED WORKSFORME http://www.w3.org/TR/html5/video.html#playing-the-media-resource a11y, media P2 normal --- 1 gez.lemon ian cooper ian mike philipj public-html-admin public-html-wg-issue-tracking silviapfeiffer1 public-html-bugzilla oldest_to_newest 31027 0 gez.lemon 2010-01-14 11:05:49 +0000 The specification states: "If the media element's Document stops being a fully active document, then the playback will stop until the document is active again." This implies that it would not be possible for a user to listen to audio in the background or take notes about a video in another application while viewing the video at the same time. Suggest that the decision about what should be done in this case should be left to the user agent. 31034 1 philipj 2010-01-14 11:46:03 +0000 If you follow the reference to http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#fully-active and then some you'll see that "active document" has to do with history navigation, not tabs or anything like this. I reported this same issue perhaps a year ago based on the same misunderstanding. 31066 2 philipj 2010-01-15 08:34:10 +0000 What does this bug even mean? User agents are already free to ignore autoplay if that's what you mean. They are also free to provide features for blocking audio/video on a per-origin basis if they want, and can pretend that the network is down for the DOM API to be in a sane state. 31067 3 philipj 2010-01-15 08:35:11 +0000 (In reply to comment #2) > What does this bug even mean? User agents are already free to ignore autoplay > if that's what you mean. They are also free to provide features for blocking > audio/video on a per-origin basis if they want, and can pretend that the > network is down for the DOM API to be in a sane state. > Sorry, it's morning and I didn't see my previous reply... 31454 4 cooper 2010-02-04 16:39:31 +0000 HTML Accessibility Task force has decided not to track this. 31464 5 cooper 2010-02-04 16:42:44 +0000 Removing myself from cc list, default on bug edits is to add, but I'm only acting on behalf of HTML A11Y TF which is already cc'd. 32069 6 ian 2010-02-14 11:16:58 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: As Philip says, a tab not having focus doesn't mean it's not fully active. 46540 7 cooper 2011-03-08 16:17:32 +0000 Bug triage sub-team agrees "worksforme" is ok resolution for this bug.