Source/core/page/RuntimeEnabledFeatures.in - Issue 18553003: Add a runtime flag for distributing extra logical height to rowspans

Side by Side Diff: Source/core/page/RuntimeEnabledFeatures.in

Issue 18553003: Add a runtime flag for distributing extra logical height to rowspans (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master

Patch Set: Created 7 years, 5 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

« no previous file with comments | « LayoutTests/tables/mozilla_expected_failures/bugs/bug6933-expected.txt ('k') | Source/core/rendering/RenderTableSection.cpp » ('j') | Source/core/rendering/RenderTableSection.cpp » ('J')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

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 50 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
61 MediaSource status=experimental	61 MediaSource status=experimental

62 MediaStream status=stable	62 MediaStream status=stable

63 Notifications status=stable	63 Notifications status=stable

64 PagePopup status=stable	64 PagePopup status=stable

65 ParseSVGAsHTML	65 ParseSVGAsHTML

66 PeerConnection depends_on=MediaStream, status=stable	66 PeerConnection depends_on=MediaStream, status=stable

67 ProgrammaticScrollNotifications status=test	67 ProgrammaticScrollNotifications status=test

68 Promise status=test	68 Promise status=test

69 Quota status=stable	69 Quota status=stable

70 RequestAutocomplete status=test	70 RequestAutocomplete status=test

	71 RowSpanLogicalHeightSpreading
	Julien - ping for review 2013/07/02 17:39:28 I don't think we should have the feature disabled I don't think we should have the feature disabled by default when testing. We know the regressions, it's just important that they don't impact our users. That means that this should be status=test so that it's enabled when testing. a.suchit 2013/07/02 18:33:35 If I use status=true for runtimeEnabledFeature the Show quoted text On 2013/07/02 17:39:28, Julien Chaffraix wrote: > I don't think we should have the feature disabled by default when testing. We > know the regressions, it's just important that they don't impact our users. > > That means that this should be status=test so that it's enabled when testing. If I use status=true for runtimeEnabledFeature then it will show many regression. is it ok for you? Julien - ping for review 2013/07/02 19:08:58 That's intended. It will limit the feature to test Show quoted text On 2013/07/02 18:33:35, a.suchit wrote: > On 2013/07/02 17:39:28, Julien Chaffraix wrote: > > I don't think we should have the feature disabled by default when testing. We > > know the regressions, it's just important that they don't impact our users. > > > > That means that this should be status=test so that it's enabled when testing. > > If I use status=true for runtimeEnabledFeature then it will show many > regression. is it ok for you? That's intended. It will limit the feature to testing thus your code gets tested as you develop but we prevent people from experiencing the regressions in regular builds. BTW, it's status=test not true.
71 ScriptedSpeech status=stable	72 ScriptedSpeech status=stable

72 SeamlessIFrames status=experimental	73 SeamlessIFrames status=experimental

73 SessionStorage status=stable	74 SessionStorage status=stable

74 SharedWorker custom	75 SharedWorker custom

75 SpeechInput status=stable	76 SpeechInput status=stable

76 SpeechSynthesis status=experimental	77 SpeechSynthesis status=experimental

77 Stream status=experimental	78 Stream status=experimental

78 StyleScoped status=experimental	79 StyleScoped status=experimental

79 Touch status=stable	80 Touch status=stable

80 Vibration status=test	81 Vibration status=test

81 VideoTrack status=stable	82 VideoTrack status=stable

82 WebAnimations	83 WebAnimations

83 WebAudio condition=WEB_AUDIO, status=stable	84 WebAudio condition=WEB_AUDIO, status=stable

84 WebGLDraftExtensions status=experimental	85 WebGLDraftExtensions status=experimental

85 WebMIDI status=test	86 WebMIDI status=test

86 WebKitMediaSource status=stable	87 WebKitMediaSource status=stable

87 WOFF2 status=experimental	88 WOFF2 status=experimental

OLD	NEW