Rename Experimental Framework classes and concepts

third_party/WebKit/Source/platform/RuntimeEnabledFeatures.in

 // http://dev.chromium.org/blink/runtime-enabled-features
 //
 // This list is used to generate RuntimeEnabledFeatures.h/cpp which contains
 // a class that stores static enablers for all experimental features.
 //
 // Each feature can be assigned a "status":
 // status=stable -> Enable this in all Blink configurations.  We are committed to these APIs indefinitely.
 // status=experimental -> In-progress features, Web Developers might play with, but are not on by default in stable.
 // status=test -> Enabled in ContentShell for testing, otherwise off.
 // Features without a status are not enabled anywhere by default.
 //
 // "implied_by" or "depends_on" specifies relationship to other features:
 // implied_by=feature1[,feature2,...] -> The feature is automatically enabled if any implied_by features is enabled;
 // depends_on=feature1[,feature2,...] -> The feature is enabled only if all depends_on features are enabled.
 // Only one of "implied_by" and "depends_on" can be specified.
 //
 // "stable" features listed here should be rare, as anything which we've shipped stable
 // can have its runtime flag removed soon after.
 //
 // condition=ENABLE_NAME is used for wrapping features in compile-time
 // #if ENABLE(FEATURE) guards.  These are deprecated and should all be removed.
 //
-// api_name=API_NAME is used to integrate the feature with the experimental framework, so that the feature can be
-// enabled at runtime on a per-page basis through a signed API key for the corresponding API name.
-// Declaring the api_name will cause a static method to be generated in
-// ExperimentalFeatures.h/cpp. This static method allows the feature
-// implementation to check if it is enabled for the current context.
+// origin_trial_feature_name=FEATURE_NAME is used to integrate the feature with the experimental framework, so that the
+// feature can be enabled at runtime on a per-page basis through a signed token for the corresponding feature name.
+// Declaring the origin_trial_feature_name will cause a static method to be generated in OriginTrials.h/cpp. This static
+// method allows the feature implementation to check if it is enabled for the current context.
 
 AppBanner status=stable
 AlwaysUseComplexText status=stable
 ApplicationCache status=stable
 AudioOutputDevices status=stable
 AudioVideoTracks depends_on=Media, status=experimental
 AuthorShadowDOMForAnyElement
 BackgroundSync status=stable
 BackgroundSyncV2 status=experimental
 CacheStorageMatchAll status=stable
@@ skipping 37 matching lines @@
 ExecCommandInJavaScript status=test
 ComputedAccessibilityInfo status=experimental
 EventListenerOptions status=stable
 ExperimentalCanvasFeatures status=test
 ExperimentalContentSecurityPolicyFeatures status=experimental
 ExperimentalFramework status=test
 // Define a sample API for testing integration with the Experimental Framework.
 // The sample API is used in both unit and layout tests for the Experimental
 // Framework. Do not change this flag to stable, as it exists solely to generate
 // code used by the sample API implementation.
-ExperimentalFrameworkSampleAPI api_name=Frobulate
+ExperimentalFrameworkSampleAPI origin_trial_feature_name=Frobulate
 ExperimentalV8Extras status=experimental
 FastMobileScrolling
 FileAPIBlobClose status=experimental
 FileSystem status=stable
 ForeignFetch status=experimental
 FormDataNewMethods status=experimental
 FullscreenUnprefixed status=test
 FrameTimingSupport status=experimental
 Geofencing status=experimental
 GeometryInterfaces status=test
@@ skipping 112 matching lines @@
 WebVR depends_on=GeometryInterfaces, status=test
 WebVTTRegions depends_on=Media, status=experimental
 V8IdleTasks
 XSLT status=stable
 smil status=stable
 ScrollCustomization
 ScrollRestoration status=stable
 WakeLock status=experimental
 WebFontsIntervention status=stable
 Worklet