- From: <bugzilla@jessica.w3.org>
- Date: Wed, 24 Sep 2014 02:28:49 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26372 --- Comment #30 from David Dorwin <ddorwin@google.com> --- (In reply to Boris Zbarsky from comment #29) > > As an example, the array model doesn't work because we need names/values not > > positions and old values. > > In the array model, the change record would presumably have the old array > and the new array, and the actual change would be a change in which array > object is returned, not in-place mutations of an array object. That's one possible solution (if MediaKeySession was observable). However, it doesn't really help applications much. I'm assuming the main benefit of observable would be if the UA could tell applications that keyY was added and keyX's status changed. Otherwise, the application can just as easily track the old and new states using the current simple event and method model. I think the ideal solution is something like the array model in the example [1] (not returning an actual array from MediaKeySession) but that provides different types of information. It might help to ignore MediaKeySession and focus on an object that represents a map of names (key IDs) to values (status enums). Could it be designed such that Object.observe() be used with that object to find out when a name is added/removed and when its value changes. If so, and once that's designed, we'd figure out how to expose that object from mediaKeySession. [1] http://wiki.ecmascript.org/doku.php?id=harmony:observe_api_usage#array -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 24 September 2014 02:28:51 UTC