Change ACCELERATED_COMPOSITING blacklist to GPU_COMPOSITING.

extensions/common/manifest_handlers/requirements_info.cc

Index: extensions/common/manifest_handlers/requirements_info.cc
diff --git a/extensions/common/manifest_handlers/requirements_info.cc b/extensions/common/manifest_handlers/requirements_info.cc
index bc26170d91a05f329d092d8e54a6cf082da28483..25ba7a4bd63881b358d75090ecbd4f4e9b29f3c0 100644
--- a/extensions/common/manifest_handlers/requirements_info.cc
+++ b/extensions/common/manifest_handlers/requirements_info.cc
@@ -18,7 +18,6 @@ namespace errors = manifest_errors;
 
 RequirementsInfo::RequirementsInfo(const Manifest* manifest)
     : webgl(false),
-      css3d(false),
       npapi(false),
       window_shape(false) {
   // Before parsing requirements from the manifest, automatically default the
@@ -120,8 +119,6 @@ bool RequirementsHandler::Parse(Extension* extension, base::string16* error) {
         if ((*feature_iter)->GetAsString(&feature)) {
           if (feature == "webgl") {
             requirements->webgl = true;
-          } else if (feature == "css3d") {

[Marijn Kruisselbrink, 2014/04/16 20:39:14]

Removing this if entirely makes this a backwards incompatible change. Extensions
that specify the css3d requirement would now always give an error (since now the
else below would be reached). I think the right thing to do would be to silently
ignore (but not reject) the css3d feature? (at least I understand that now what
the css3d feature specified will always be available)

[danakj, 2014/04/16 20:46:57]

oh ok that was what I was attempting to do yes. i guess i messed that up here. 

[danakj, 2014/04/16 20:54:11]

I'm trying to understand what the right thing to do here is. I don't see "css3d"
or even "3D" in the manifest_constants.cc file. Would branching and doing
nothing here be the right thing? Should I leave this code alone and just change
the RequirementsChecker?

-            requirements->css3d = true;
           } else {
             *error = ErrorUtils::FormatErrorMessageUTF16(
                 errors::kInvalidRequirement, iter.key());