- From: <bugzilla@jessica.w3.org>
- Date: Tue, 23 Apr 2013 18:48:18 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21798 --- Comment #5 from Joe Steele <steele@adobe.com> --- Here is what I would see Adobe Access using as errors: MEDIA_KEYERR_UNKNOWN -- We would use this for debugging, but these are generally unrecoverable MEDIA_KEYERR_CLIENT -- We would use this to say that we failed to install or initialize the CDM -- This could be actionable if the user has the option to deny the CDM from being installed and/or launched MEDIA_KEYERR_SERVICE -- This could translate to any number of service related errors on our side for example: activation failure, license acquisition failure, in-band authentication failure, etc. -- I think making this actionable requires more detail, which could be provide by a systemCode. MEDIA_KEYERR_OUTPUT -- We would use this to handle all output related errors. -- This is typically actionable by the user by unplugging the offending output devices. MEDIA_KEYERR_HARDWARECHANGE -- This seems like a dup to me of the above error code and we would not use it. MEDIA_KEYERR_DOMAIN -- We would use this to represent domain specific service errors. -- This would be actionable by attempting to re-register to the domain. I would like to see an additional error -- MEDIA_KEYERR_EXPIRED -- We would use this to represent that the current key(s) have expired and need to be re-requested -- This is actionable and the solution is to re-create the session -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 23 April 2013 18:48:19 UTC