Unified BeginFrame scheduling

content/public/common/content_switches.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "content/public/common/content_switches.h"
 
 #include "base/command_line.h"
 
 namespace switches {
 
@@ skipping 297 matching lines @@
 const char kEnableDistanceFieldText[]       = "enable-distance-field-text";
 
 // Enables experimental feature that maps multiple RenderLayers to
 // one composited layer to avoid pathological layer counts.
 const char kEnableLayerSquashing[] =
     "enable-layer-squashing";
 
 // Enable experimental container node culling.
 const char kEnableContainerCulling[]        = "enable-container-culling";
 
-// Use a BeginFrame signal from browser to renderer to schedule rendering.
-const char kEnableBeginFrameScheduling[]    = "enable-begin-frame-scheduling";
-
 // Enable the creation of compositing layers for fixed position
 // elements. Three options are needed to support four possible scenarios:
 //  1. Default (disabled)
 //  2. Enabled always (to allow dogfooding)
 //  3. Disabled always (to give safety fallback for users)
 //  4. Enabled only if we detect a highDPI display
 //
 // Option #4 may soon be the default, because the feature is needed soon for
 // high DPI, but cannot be used (yet) for low DPI. Options #2 and #3 will
 // override Option #4.
@@ skipping 619 matching lines @@
 // Enable the Win32K process mitigation policy for renderer processes which
 // prevents them from invoking user32 and gdi32 system calls which enter
 // the kernel. This is only supported on Windows 8 and beyond.
 const char kEnableWin32kRendererLockDown[]
     = "enable_win32k_renderer_lockdown";
 #endif
 
 // Don't dump stuff here, follow the same order as the header.
 
 }  // namespace switches