Expose WEBGL_debug_renderer_info through a chromium finch experiment.

public/web/WebPermissionClient.h

 /*
  * Copyright (C) 2011 Google Inc. All rights reserved.
  *
  * Redistribution and use in source and binary forms, with or without
  * modification, are permitted provided that the following conditions are
  * met:
  *
  *     * Redistributions of source code must retain the above copyright
  * notice, this list of conditions and the following disclaimer.
  *     * Redistributions in binary form must reproduce the above
@@ skipping 83 matching lines @@
     virtual bool allowWebComponents(const WebDocument&, bool defaultValue) { return defaultValue; }
 
     // Controls whether to enable MutationEvents for this document.
     // The common use case of this method is actually to selectively disable MutationEvents,
     // but it's been named for consistency with the rest of the interface.
     virtual bool allowMutationEvents(const WebDocument&, bool defaultValue) { return defaultValue; }
 
     // Controls whether pushState and related History APIs are enabled for this frame.
     virtual bool allowPushState(const WebDocument&) { return true; }
 
+    // Controls whether WebGL extension WEBGL_debug_renderer_info is allowed for this frame.
+    virtual bool allowWebGLDebugRendererInfo(WebFrame*) { return false; }

[abarth-chromium, 2013/10/30 21:41:56]

This should take a const WebDocument& like the other per-context features.

[Zhenyao Mo, 2013/10/30 21:57:11]

I am confused.  There are multiple examples using WebFrame (allowStorage,
allowWriteToClipboard) and multiple examples using WebDocument, what's the
difference?

+
     // Notifies the client that the frame would have instantiated a plug-in if plug-ins were enabled.
     virtual void didNotAllowPlugins(WebFrame*) { }
 
     // Notifies the client that the frame would have executed script if script were enabled.
     virtual void didNotAllowScript(WebFrame*) { }
 
 protected:
     ~WebPermissionClient() { }
 };
 
 } // namespace WebKit
 
 #endif