third_party/WebKit/Source/platform/RuntimeEnabledFeatures.in - Issue 2472583003: Navigation Timing Level 2

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

Issue 2472583003: Navigation Timing Level 2 (Closed)

Patch Set: added two TODOs and attached crbugs Created 4 years, 1 month ago

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

Jump to:

« third_party/WebKit/Source/core/timing/PerformanceBase.cpp ('K') | « third_party/WebKit/Source/core/timing/PerformanceResourceTiming.cpp ('k') | no next file » | 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 // Features without a status are not enabled anywhere by default.	10 // Features without a status are not enabled anywhere by default.

(...skipping 247 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
258 WakeLock status=experimental	258 WakeLock status=experimental

259 WebFontsInterventionV2With2G	259 WebFontsInterventionV2With2G

260 WebFontsInterventionV2With3G	260 WebFontsInterventionV2With3G

261 WebFontsInterventionV2WithSlow2G	261 WebFontsInterventionV2WithSlow2G

262 WebFontsInterventionTrigger	262 WebFontsInterventionTrigger

263 WebShare status=experimental, origin_trial_feature_name=WebShare, origin_trial_o s=android	263 WebShare status=experimental, origin_trial_feature_name=WebShare, origin_trial_o s=android

264 Worklet status=experimental	264 Worklet status=experimental

265 LazyParseCSS status=experimental	265 LazyParseCSS status=experimental

266 ParseHTMLOnMainThread status=test	266 ParseHTMLOnMainThread status=test

267 SendBeaconThrowForBlobWithNonSimpleType status=experimental	267 SendBeaconThrowForBlobWithNonSimpleType status=experimental

	268 PerformanceNavigationTiming2 status=test
	kinuko 2016/11/08 13:39:32 status=test is not super useful esp. without test status=test is not super useful esp. without test code. You probably want status=experimental instead (therefore developers can try out the feature with experimental flag)? Oh, btw-- have you already sent intent to implement email? panicker 2016/11/08 18:27:06 Jian is adding Layout tests. We want to flip to "e Show quoted text On 2016/11/08 13:39:32, kinuko wrote: > status=test is not super useful esp. without test code. You probably want > status=experimental instead (therefore developers can try out the feature with > experimental flag)? > > Oh, btw-- have you already sent intent to implement email? Jian is adding Layout tests. We want to flip to "experimental" when the implementation is complete (i.e. major TODOs are resolved) Also drafted and just sending Intent: https://docs.google.com/document/d/1z0gzmvJKtoA3pjXz9UXy2KvtnNire0eV9mzb5usEg... sunjian 2016/11/08 23:16:21 Acknowledged. Show quoted text On 2016/11/08 13:39:32, kinuko wrote: > status=test is not super useful esp. without test code. You probably want > status=experimental instead (therefore developers can try out the feature with > experimental flag)? > > Oh, btw-- have you already sent intent to implement email? Acknowledged.
	269

OLD	NEW