- From: <bugzilla@jessica.w3.org>
- Date: Thu, 28 Jul 2011 02:09:40 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13383 --- Comment #3 from John Foliot <jfoliot@stanford.edu> 2011-07-28 02:09:39 UTC --- (In reply to comment #2) > I think you're right about background music -- and also for radio, podcasts, etc. > However, I think there is still a need for pausing video on hidden pages. > > I can imagine a video player with a Pause If Hidden control, on by default -- > though I also have doubts that many users would understand or use this. > > User agent mute/unmute/pause/unpause functionality sounds useful, but it > doesn't solve the problem of opening multiple video links (in hidden > tabs/windows) or when navigating between tabs/windows, each with playing media. Just to add an additional data-point here re: Audio. While looking at accessibility of <audio> there will be instances where the content author has included captioning associated to the audio-stream (think speeches, podcasts, etc.): in those instances adding accessible audio would actually require using the <video> element as that would be the only way to also include a region for visible (supporting) content, such as those caption files (or perhaps sign-language interpretation). Yet there is a strong likelihood that not all content consumers will require those supporting visual aids (and may want to have the audio portion in a background tab), so for your use-cases making a distinction between audio and video will introduce potentially unintended negative behaviors. I suspect that what is really required is that auto-start be disabled if a page is not visible, but once a stream is started, the end user can choose to send it to a non-visible tab/window without silencing the audio stream FWIW -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 28 July 2011 02:09:45 UTC