Don't require VDAs to return all PictureBuffers at once.

media/video/video_decode_accelerator.h

Index: media/video/video_decode_accelerator.h
diff --git a/media/video/video_decode_accelerator.h b/media/video/video_decode_accelerator.h
index e2bcdf64855fdf3455fc0a3b73ae2b59c2e928e6..442327de84dd8da6836c5536697de549f792a1ac 100644
--- a/media/video/video_decode_accelerator.h
+++ b/media/video/video_decode_accelerator.h
@@ -34,6 +34,22 @@ class MEDIA_EXPORT VideoDecodeAccelerator {
   };
   using SupportedProfiles = std::vector<SupportedProfile>;
 
+  struct MEDIA_EXPORT Capabilities {
+    Capabilities();
+    ~Capabilities();
+    // Flags that can be associated with a VDA.
+    enum Flags {
+      kNoFlags = 0,

[sandersd (OOO until July 31), 2015/12/04 19:10:24]

And now here we've ended up with two different enum styles in the same file. I
don't even know what I want anymore :-(

(Relatedly: there were at least two chromium-dev threads about bitfield enums,
and they didn't come to any conclusions other than that contexpr is still
banned.)

[liberato (no reviews please), 2015/12/07 19:04:39]

true.  changed to NO_FLAGS to be consistent. changing everything else to
kIllegalState is just too much for this CL.

+
+      // If set, then the VDA makes no guarantees that it won't stall before
+      // sending all the picture buffers to the client via PictureReady.
+      kCanStallAnytime = 1 << 0,
+    };
+
+    SupportedProfiles supported_profiles;
+    Flags flags;
+  };
+
   // Enumeration of potential errors generated by the API.
   // Note: Keep these in sync with PP_VideoDecodeError_Dev. Also do not
   // rearrange, reuse or remove values as they are used for gathering UMA