Document GetIntegerv errors in ANGLE_framebuffer_blit.

git-svn-id: https://angleproject.googlecode.com/svn/branches/dx11proto@1778 736b8ea6-26fd-11df-bfd4-992fa37f6226

extensions/ANGLE_framebuffer_blit.txt

@@ -24,8 +24,8 @@ Status
 
 Version
 
-    Last Modified Date: Aug 6, 2010
-    Author Revision: 3
+    Last Modified Date: Sept 22, 2012
+    Author Revision: 4
 
 Number
 
@@ -109,7 +109,11 @@ Operations and the Framebuffer)
 
     "Calling ReadPixels generates INVALID_FRAMEBUFFER_OPERATION if
     the object bound to READ_FRAMEBUFFER_BINDING_ANGLE is not "framebuffer
-    complete" (section 4.4.4.2)."
+    complete" (section 4.4.4.2). GetIntegerv generates an INVALID_OPERATION
+    error if the object bound to READ_FRAMEBUFFER_BINDING_ANGLE is not
+    framebuffer complete, or if the GL is using a framebuffer object 
+    (i.e. READ_FRAMEBUFFER_BINDING_ANGLE is non-zero) and there is no color
+    attachment."
 
     Insert a new section 4.3.2 titled "Copying Pixels" and renumber the
     subsequent sections.  Add the following text:
@@ -314,6 +318,10 @@ Errors
     BlitFramebufferANGLE, ReadPixels, CopyTex{Sub}Image*, is called while the
     read framebuffer is not framebuffer complete.
 
+    The error INVALID_OPERATION is generated if GetIntegerv is called
+    while the read framebuffer is not framebuffer complete, or if there
+    is no color attachment present on the read framebuffer object.
+
     The error INVALID_VALUE is generated by BlitFramebufferANGLE if
     <mask> has any bits set other than those named by
     COLOR_BUFFER_BIT, DEPTH_BUFFER_BIT or STENCIL_BUFFER_BIT.
@@ -424,4 +432,6 @@ Revision History
       - improve some error language
     Revision 3, 2010/08/06
       - add additional contributors, update implementation status
+    Revision 4, 2012/09/22
+      - document errors for GetIntegerv.