Implement Pepper PPB_VideoDecoder interface.

ppapi/api/pp_errors.idl

Index: ppapi/api/pp_errors.idl
diff --git a/ppapi/api/pp_errors.idl b/ppapi/api/pp_errors.idl
index 1e4e8706aa292c1048d361dd8ff4c7d98eca7f52..7267d3ac2d200454982e115d58595c2c529467dd 100644
--- a/ppapi/api/pp_errors.idl
+++ b/ppapi/api/pp_errors.idl
@@ -178,6 +178,15 @@
   /**
    * This value indicates that the host name could not be resolved.
    */
-  PP_ERROR_NAME_NOT_RESOLVED = -110
+  PP_ERROR_NAME_NOT_RESOLVED = -110,
+  /**
+   * This value indicates that plugin passed bad input data to the browser.
+   */
+  PP_ERROR_UNREADABLE_INPUT = -111,

[dmichael (off chromium), 2014/05/08 20:27:00]

Hmm, I'm a little unsure about this error code. It does seem to be more info
than BAD_ARGUMENT, but "unreadable input" doesn't sound right to me, either.
It's "readable", it just (if I understand right) doesn't conform to the expected
format.

What do you think of:
PP_ERROR_DATA_INVALID
or
PP_ERROR_CONTENT_INVALID

[bbudge, 2014/05/14 16:40:41]

I struggled with this one. My first thought was PP_ERROR_MALFORMED_INPUT but I
decided to just add what was needed for this API. Your preference?

+  /**
+   * This value indicates that a platform failure occurred. This indicates that
+   * the browser could not complete a valid request from the plugin.
+   */
+  PP_ERROR_PLATFORM_FAILED = -112

[dmichael (off chromium), 2014/05/08 20:27:00]

This one makes me a little sad. We're exposing more platform differences. But I
think it's probably a good idea to add the new error, rather than hide it behing
PP_ERROR_FAILED.

[bbudge, 2014/05/14 16:40:41]

Yes. I'm not adding these lightly. The existing error codes just don't seem
appropriate for these.

 };