- From: <bugzilla@jessica.w3.org>
- Date: Tue, 16 Sep 2014 15:08:45 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26776
Mark Watson <watsonm@netflix.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |watsonm@netflix.com
--- Comment #3 from Mark Watson <watsonm@netflix.com> ---
(In reply to Anne from comment #2)
> a) Why is only Microsoft interested in this? b) Can this be something that
> just goes to the developer console?
Not just Microsoft. We think this it is essential to have access to the system
error code. I believe Adobe also.
In practice rolling out EME, we initially see an unacceptable level of errors
which we had not previously seen during testing. Often this is due to platform
diversity. It's essential to have the low-level cause reported to our servers
for detecting and debugging these.
>
> I made a ton of comments against having proprietary exception codes in bug
> 25896.
The situation with EME is somewhat special because we are providing an API to
what is likely a component with proprietary functionality. The merits of that
have been extensively debated on the public-restricted-media list, but given
that fact and the practical deployment experience, I think exposing a system
code is justified here.
Having said that, it's not clear to me why we could not simply define a
recommended convention for the message field in the EME case - for example that
it begin with a numeric code followed by whitespace.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 16 September 2014 15:08:48 UTC