W3C home > Mailing lists > Public > public-html-media@w3.org > March 2015

[encrypted-media] MediaKeyStatusMap: Replace maplike with explicit methods

From: ddorwin via GitHub <sysbot+gh@w3.org>
Date: Mon, 09 Mar 2015 23:54:18 +0000
To: public-html-media@w3.org
Message-ID: <issues.opened-60429856-1425945258-sysbot+gh@w3.org>
ddorwin has just created a new issue for 
https://github.com/w3c/encrypted-media:

== MediaKeyStatusMap: Replace maplike with explicit methods ==
Issue #25 identified problems with our use of maplike - specifically 
that BufferSource objects will be compared rather than the key IDs 
they contain. (Issue is also #24 related to maplike.)

It does not sound like the maplike behavior will change in a way that 
solves #25 (see the thread at 
https://lists.w3.org/Archives/Public/public-script-coord/2015JanMar/0148.html
 for more discussion), so we should move forward without maplike. (If 
compatible functionality is later added, we should be able to switch 
back without breaking application compatibility.)

I propose replacing `MediaKeyStatusMap`'s
>`readonly maplike<BufferSource, MediaKeyStatus>;`

with (a subset of the) explicit members that `readonly maplike` added 
(entries, forEach, get, has, keys, values, `@@iterator` methods and a 
size getter).

Shall we include all methods and the size getter? Do we need 
[`@@iterator`](https://people.mozilla.org/~jorendorff/es6-draft.html#sec-well-known-symbols)
 if the object does not have bindings to an ES Map?

See https://github.com/w3c/encrypted-media/issues/39
Received on Monday, 9 March 2015 23:54:20 UTC

This archive was generated by hypermail 2.3.1 : Monday, 9 March 2015 23:54:20 UTC