[Bug 25923] isTypeSupported should be asynchronous

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25923

David Dorwin <ddorwin@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ddorwin@google.com

--- Comment #1 from David Dorwin <ddorwin@google.com> ---
isTypeSupported() is intended to allow applications use multiple calls to
quickly and systematically find a supported key system and media combination.
I'm not sure how that would work if it was asynchronous.

Is isTypeSupported() a good time to prompt the user? Applications are likely to
call it multiple times for various key systems and media types.

There might be other advantages to it being asynchronous and supporting prompts
(i.e. preventing abuse of the information), but I'm not sure how to address the
issues above, at least with the current design. Maybe a
constraints/capabilities-based design would address this by allowing an
application to provide all its supported configurations and get a response in
one call.


For the specific scenario in comment #0, how about returning "maybe" from
isTypeSupported() and waiting for MediaKeys.create() to prompt?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 30 May 2014 17:16:11 UTC