[Bug 26332] Applications should only use EME APIs on secure origins (e.g. HTTPS)

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

--- Comment #14 from Joe Steele <steele@adobe.com> ---
> Chrome. It's working now after I cleared browsing data and restarted my
> machine. Don't really know what the problem was.
> 
> The point is that SSL introduces additional failure modes and we have
> measured this in the field. For our service, we have a baseline for our
> playback failure rate which, according to our measurements, it is not
> possible to achieve if there is SSL involved even on the browser that is
> 'best' in this area (and the 'best' here is much better than the rest).

As another piece of anecdotal evidence for problems like this - I had a similar
problem with Chrome (Chrome rejecting the SSL certificate for google.com). It
turned out to be a misconfiguration of the time server on my machine. No amount
of Chrome configuration seemed to fix the problem. I don't mean to imply Chrome
is alone in these problems -- all the browsers have them. The problem is more
in how we present errors to the user, than in the browsers doing something
wrong.

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

Received on Thursday, 24 July 2014 19:53:49 UTC