- From: <bugzilla@jessica.w3.org>
- Date: Tue, 03 Apr 2012 16:23:32 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16617 Summary: Consider more granular error reporting Product: HTML WG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: Encrypted Media Extensions AssignedTo: adrianba@microsoft.com ReportedBy: watsonm@netflix.com QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org MEDIA_ERR_ENCRYPTED covers three cases 1) No key was provided and no needkey handler was provided 2) The provided key could not be successfully applied 3) The user agent does not support decryption of this media data Consider whether these should be differentiated ? A single error is consistent with the current broad error codes, though that may be something that should be improved in general. It seems that except for #1, which should only occur in applications that do not support encrypted media, these are all application bugs and not something that would improve the user experience. Any unique handling of the error codes by an application would essentially be describing a bug type. Unique codes might be helpful in tracking down the cause of the bug, but there are probably other options. It is also possible that some of these cases should be reported via MediaKeyErrorEventInit. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 3 April 2012 16:23:39 UTC