From 250ff7b97e979172fd88ab1b01d24579eb115c89 Mon Sep 17 00:00:00 2001 From: "kbr@chromium.org" Date: Wed, 23 Mar 2011 19:07:29 +0000 Subject: If --disable-webgl is passed, continue to return null from Canvas.getContext("webgl"), but leave WebGLRenderingContext and related properties on the DOMWindow. Blacklisting of certain GPUs is resulting in reports that the browser doesn't support WebGL, when in reality only the graphics card doesn't. An upstream WebKit patch will follow this one removing the WebGL switch from WebRuntimeFeatures and removing the EnabledAtRuntime extended attribute from these properties. BUG=77110 TEST=none (verified manually) R=tony@chromium.org,darin@chromium.org,arv@chromium.org Review URL: http://codereview.chromium.org/6705015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@79160 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/browser/renderer_host/browser_render_process_host.cc | 5 ----- 1 file changed, 5 deletions(-) (limited to 'chrome/browser/renderer_host') diff --git a/chrome/browser/renderer_host/browser_render_process_host.cc b/chrome/browser/renderer_host/browser_render_process_host.cc index bfc5881..ec7ae7d 100644 --- a/chrome/browser/renderer_host/browser_render_process_host.cc +++ b/chrome/browser/renderer_host/browser_render_process_host.cc @@ -680,11 +680,6 @@ void BrowserRenderProcessHost::PropagateBrowserCommandLineToRenderer( switches::kDisableDatabases, switches::kDisableDesktopNotifications, switches::kDisableDeviceOrientation, - // We need to propagate this flag to determine whether to make the - // WebGLArray constructors on the DOMWindow visible. This - // information is needed very early during bringup. We prefer to - // use the WebPreferences to set this flag on a page-by-page basis. - switches::kDisableExperimentalWebGL, switches::kDisableFileSystem, switches::kDisableGeolocation, switches::kDisableGLMultisampling, -- cgit v1.1