This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24213 - MediaKeyNeededEvent's "type" attribute conflicts with Event's "type" attribute
Summary: MediaKeyNeededEvent's "type" attribute conflicts with Event's "type" attribute
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Encrypted Media Extensions (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: Adrian Bateman [MSFT]
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2014-01-06 18:17 UTC by David Dorwin
Modified: 2014-01-07 17:19 UTC (History)
3 users (show)

See Also:


Description David Dorwin 2014-01-06 18:17:09 UTC
The current definition of MediaKeyNeededEvent [1] includes an attribute named "type", which provides the value to pass to createSession()'s "type" parameter [2]. The problem is that Event [3], which MediaKeyNeededEvent inherits from, also has a "type" attribute that means something very different.

We need to rename the "type" attribute on MediaKeyNeededEvent and probably the createSession() parameter as well for consistency.

* "type" was originally selected as the parameter name because it is similar to the same parameter in canPlayType().
* The "type" attribute was later added in bug 19096.

Comment 1 Pavel Pergamenshchik 2014-01-06 20:14:43 UTC
How about "mimeType"?

isTypeSupported takes a "type" as well, if we are going for overall consistency.
Comment 2 Adrian Bateman [MSFT] 2014-01-07 16:23:32 UTC
I propose we use contentType, since this matches the header. I think it is okay to rename the arguments too.
Comment 3 Adrian Bateman [MSFT] 2014-01-07 17:19:41 UTC