- From: <bugzilla@jessica.w3.org>
- Date: Tue, 26 Mar 2013 05:17:32 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19009 --- Comment #3 from Jer Noble <jer.noble@apple.com> --- (In reply to comment #2) > I don't think there's any reason why a single MediaKeys object couldn't be > used with more than one media element. It is possible you might want to > share keys, especially when we resolve bug 19208 so that we know how to keep > playing if you already have the key information you need. There's at least one good reason, listed above: it makes object lifetime management very hairy. This would be the first and only DOM object which can have multiple parents. > This could be a quality of implementation issue. Media engines in user > agents may support key sharing up to a certain number of elements (perhaps > that limit is 1). It is likely that early implementations would do so after > setting once but we shouldn't unnecessarily constrain future > implementations. I propose that we update the spec to throw QUOTA_EXCEEDED > exception or something similar if the limit has been reached. If you want MediaKeys objects to share keys, you should make that an explicit feature of the specification, rather than a side effect of a non-standard ownership model. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 26 March 2013 05:17:33 UTC