Source/platform/RuntimeEnabledFeatures.in - Issue 639773007: Enable V8 idle tasks.

Side by Side Diff: Source/platform/RuntimeEnabledFeatures.in

Issue 639773007: Enable V8 idle tasks. (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Created 6 years, 2 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

« Source/bindings/core/v8/V8Initializer.cpp ('K') | « Source/bindings/core/v8/V8Initializer.cpp ('k') | Source/web/WebRuntimeFeatures.cpp » ('j') | no next file with comments »

OLD	NEW
1 // http://dev.chromium.org/blink/runtime-enabled-features	1 // http://dev.chromium.org/blink/runtime-enabled-features

2 //	2 //

3 // This list is used to generate RuntimeEnabledFeatures.h/cpp which contains	3 // This list is used to generate RuntimeEnabledFeatures.h/cpp which contains

4 // a class that stores static enablers for all experimental features.	4 // a class that stores static enablers for all experimental features.

5 //	5 //

6 // Each feature can be assigned a "status":	6 // Each feature can be assigned a "status":

7 // status=stable -> Enable this in all Blink configurations. We are committed t o these APIs indefinitely.	7 // status=stable -> Enable this in all Blink configurations. We are committed t o these APIs indefinitely.

8 // status=experimental -> In-progress features, Web Developers might play with, but are not on by default in stable.	8 // status=experimental -> In-progress features, Web Developers might play with, but are not on by default in stable.

9 // status=test -> Enabled in ContentShell for testing, otherwise off.	9 // status=test -> Enabled in ContentShell for testing, otherwise off.

10 // status=deprecated -> Alias for "test", will be removed at some point.	10 // status=deprecated -> Alias for "test", will be removed at some point.

(...skipping 122 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
133 Touch status=stable	133 Touch status=stable

134 TouchIconLoading	134 TouchIconLoading

135 UserSelectAll status=experimental	135 UserSelectAll status=experimental

136 WebAnimationsAPI status=experimental	136 WebAnimationsAPI status=experimental

137 WebAnimationsPlaybackControl status=stable	137 WebAnimationsPlaybackControl status=stable

138 WebAudio condition=WEB_AUDIO, status=stable	138 WebAudio condition=WEB_AUDIO, status=stable

139 WebGLDraftExtensions status=experimental	139 WebGLDraftExtensions status=experimental

140 WebGLImageChromium	140 WebGLImageChromium

141 WebMIDI status=test	141 WebMIDI status=test

142 WebVTTRegions depends_on=Media, status=experimental	142 WebVTTRegions depends_on=Media, status=experimental

	143 V8IdleTasks status=stable
	jochen (gone - plz use gerrit) 2014/10/13 08:06:21 maybe first add the feature without a status, so i maybe first add the feature without a status, so it doesn't collide with the notifications from the compositor? jochen (gone - plz use gerrit) 2014/10/13 08:06:21 Maybe add the feature without a status first, so i Maybe add the feature without a status first, so it doesn't collide with the tasks from the compositor? then you can change the chromium side to enable the feature at the same time the compositor idle notifications are disabled jochen (gone - plz use gerrit) 2014/10/13 08:06:21 Maybe add the feature without a status first, so i Maybe add the feature without a status first, so it doesn't collide with the tasks from the compositor? then you can change the chromium side to enable the feature at the same time the compositor idle notifications are disabled jochen (gone - plz use gerrit) 2014/10/13 08:06:21 Maybe add the feature without a status first, so i Maybe add the feature without a status first, so it doesn't collide with the tasks from the compositor? then you can change the chromium side to enable the feature at the same time the compositor idle notifications are disabled rmcilroy 2014/10/13 11:22:08 Sure that makes sense - done. Show quoted text On 2014/10/13 08:06:21, jochen wrote: > Maybe add the feature without a status first, so it doesn't collide with the > tasks from the compositor? > > then you can change the chromium side to enable the feature at the same time the > compositor idle notifications are disabled Sure that makes sense - done.
143 XSLT status=stable	144 XSLT status=stable

OLD	NEW