This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Otherwise it is unclear what their values are.
(In reply to Anne from comment #0) > Otherwise it is unclear what their values are. We believe this bug refers to the text in Section 3.1: https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html#event-definitions /paulc
It does, yes. MediaKeyNeededEventInit and MediaKeyMessageEventInit in particular.
What is the notation in WebIDL for an empty ArrayBuffer ? ArrayBuffer message = ArrayBuffer(); or ArrayBuffer message = new ArrayBuffer(); or ?
https://dvcs.w3.org/hg/html-media/rev/a0f72cc27b6d
Would it be better to have an empty ArrayBuffer? We can certainly fix IDL.
Syntax wise, we could probably reuse "= []" to represent empty arraythings of all sorts.
(In reply to Mark Watson from comment #4) > https://dvcs.w3.org/hg/html-media/rev/a0f72cc27b6d Was the change to MediaKeyMessageEvent's destinationURL attribute intentional? This is the only one of the four attributes in non-Init structures to get a default value.
(In reply to David Dorwin from comment #7) > (In reply to Mark Watson from comment #4) > > https://dvcs.w3.org/hg/html-media/rev/a0f72cc27b6d > > Was the change to MediaKeyMessageEvent's destinationURL attribute > intentional? This is the only one of the four attributes in non-Init > structures to get a default value. Oops - you are right - I will fix this.
(In reply to Mark Watson from comment #8) > (In reply to David Dorwin from comment #7) > > (In reply to Mark Watson from comment #4) > > > https://dvcs.w3.org/hg/html-media/rev/a0f72cc27b6d > > > > Was the change to MediaKeyMessageEvent's destinationURL attribute > > intentional? This is the only one of the four attributes in non-Init > > structures to get a default value. > > Oops - you are right - I will fix this. I reverted the change to this line in https://dvcs.w3.org/hg/html-media/rev/a38c961e1ab0.