- From: <bugzilla@jessica.w3.org>
- Date: Tue, 30 Apr 2013 00:36:30 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20691 --- Comment #3 from David Dorwin <ddorwin@google.com> --- Similarly, should |initData| be required as well? It could be an empty array I suppose, but not allowing null would simplify code and remove the only remaining optional parameter in EME. The use case I imagine someone might want is to create a generic session for some purpose. In that case, |type| doesn't make much sense, but we've required it so why not require |initData|? It seems we should either allow both to be null (already decided not to allow |type|) or not allow either to be null. Thoughts? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 30 April 2013 00:36:31 UTC