- From: <bugzilla@jessica.w3.org>
- Date: Wed, 01 May 2013 04:27:54 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20336 David Dorwin <ddorwin@google.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |acolwell@google.com --- Comment #4 from David Dorwin <ddorwin@google.com> --- It doesn't matter too much to me - the primary downside is the extra work for implementors. How important is the declarative case given that many (most?) EME apps will use MSE as well? I'm a bit concerned that the same logic (type + key system) needs to be spread across objects to support both <source> and MediaKeys::isTypeSupported(). I don't have experience to say how big of an issue that is, though. If this makes sense for EME, does it make sense for MSE as well? I guess the assumption there is that you either support MSE for ISO/WebM or you wouldn't support any such extensions to HTMLSourceElement. Browsers that don't support MSE might get an automatic fallback without needing to make any changes, though. (If there is interest in this idea, we should file a separate bug for MSE. I'm just bringing it up here for context.) -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 1 May 2013 04:27:57 UTC