Proposed changes for Pepper 3D API.

ppapi/c/dev/pp_graphics_3d_dev.h

Index: ppapi/c/dev/pp_graphics_3d_dev.h
===================================================================
--- ppapi/c/dev/pp_graphics_3d_dev.h	(revision 98226)
+++ ppapi/c/dev/pp_graphics_3d_dev.h	(working copy)
@@ -9,7 +9,6 @@
 #include "ppapi/c/pp_stdint.h"
 
 enum PP_Graphics3DError_Dev {
-  PP_GRAPHICS3DERROR_BAD_ATTRIBUTE = 0x3004,
   PP_GRAPHICS3DERROR_CONTEXT_LOST = 0x300E
 };
 
@@ -32,8 +31,9 @@
   PP_GRAPHICS3DATTRIB_SAMPLE_BUFFERS = 0x3032,
   // Attrib list terminator.
   PP_GRAPHICS3DATTRIB_NONE = 0x3038,
-
-  // Surface-specific attributes.
+  // Boolean to ignore the alpha channel of RGBA color buffer.
+  // The value of this attribute is ignored for RGB color buffer.
+  PP_GRAPHICS3DATTRIB_BIND_RGB = 0x3039,

[piman, 2011/08/25 19:58:09]

I think we want more flexibility than this here. At least:
- pre-multiplied alpha (what is the default today)
- non-premul alpha (what many games would typically do, also available on WebGL)
- ignore alpha

See bug http://code.google.com/p/chromium/issues/detail?id=74209

I think we'd want specifying the complete blending function, as 2 enum values
for source and destination, providing the most flexibility, without adding
complexity (since we can do it all in the compositor).

[greggman, 2011/09/22 21:01:25]

Do we need that functionality here?

I'm pretty sure that's all being added to css so if you want it blended
different you just set the css.

Adding it here would then add complexity since you'd have to combine them with
the css blending modes to get the correct result.

   // Height of surface in pixels.
   PP_GRAPHICS3DATTRIB_HEIGHT = 0x3056,
   // Width of surface in pixels.