- From: <bugzilla@jessica.w3.org>
- Date: Fri, 15 Jul 2011 23:04:58 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12559 --- Comment #4 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2011-07-15 23:04:57 UTC --- (In reply to comment #3) > This would have all kinds of weird side-effects I don't think you want. For > example, say you had two <video> elements with the same mediagroup="", both > marked as autoplay="", and one is longer than the other. If we set paused to > true when a media element's playback ends, then as soon as one of the two > tracks ends, seeking back to before that point would only have the long track > playing. I think there is something weird going on with the MediaController. I only just noticed that the MediaController's paused state is true when *any* slave is paused. The way I read this, it means that when pause() is called on one slave, that this slave goes into paused state, the controller goes into paused state, but all other slaves continue playing. I think that's a mistake. The MediaController is representing the combined state of all slaves. Therefore, a MediaController's paused state should be true only when *all* slaves are paused (not when one of them is). Further, a pause() and play() call on the controller need to be propagated to all slaves - I couldn't find this in the spec. Then, the combined resource will continue playing until all slaves reach ended, at which point the controller reaches ended. Now, when all slaves have reached ended, we could put them all into paused state, which is what a combined play button would also show at this instance, thus removing the weird side-effect that you pointed out. -- 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 Friday, 15 July 2011 23:04:59 UTC