[Bug 25923] isTypeSupported should be asynchronous

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

--- Comment #14 from Boris Zbarsky <bzbarsky@mit.edu> ---
Jerry, David, with all due respect I think you're missing the point.

In order for some UAs to implement the user authorization prompts they want to
implement, they need to have isTypeSupported asynchronous.  The reason for that
is that they don't know whether the type is supported until they have
downloaded parts of a CDM that they may not be willing to download without
explicit user permission.  I'm not sure how to make this clearer.  Even if the
CDM download happens without a user prompt, the isTypeSupported call obviously
can't block on a download of a CDM over the network.

There is no "mixing up" involved, just a simple logical implication: if the UA
does not know at the time isTypeSupported is called whether the type is in fact
supported, then it cannot answer the question being asked.

This is not about looking for ways to trigger the UI.  This is just about the
fact that if the UA does not ship with the CDM to start with, then there is no
sane way to implement a synchronous isTypeSupported.

This is why discussion should happen on mailing lists (or in this case in
bugs), not calls, by the way; had you done that you would have gotten your
misconceptions corrected earlier.

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

Received on Wednesday, 27 August 2014 23:44:24 UTC