Use a single flag for enabling experimental WebKit features.

Use a single flag for enabling experimental WebKit features.

Merge multiple command line webkit features into a single flag.  This
has the benefit that when a new feature is added, we can add it to this
flag rather than requiring users to toggle another flag.  This is
similar to what extensions does for experimental APIs.

BUG=148503
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=157014

[tony, 2012-09-14 18:20:36]

This includes exclusions, regions, style scoped, shadow DOM and variables. 
Should I add anything else?  Maybe shaders?

[ojan, 2012-09-14 18:39:14]

LGTM (I'm not an owner though). I think this is great for now.

There's a few other flags that I wonder if they should also be rolled in here,
or at least also enabled if you enable this:
-Fixed position elements create stacking contexts
-Enable <track> element
-Enable Media Source API on <video> elements
-Enable Encrypted Media Extensions on <video> elements
-Pointer Lock
-Enable Experimental JavaScript
-Enable touch events

We can evaluate all those in a separate patch though and based off web developer
/ devrel feedback.

[darin (slow to review), 2012-09-14 20:25:25]

LGTM

[commit-bot: I haz the power, 2012-09-14 20:28:13]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tony@chromium.org/10917269/1

[commit-bot: I haz the power, 2012-09-14 20:42:50]

Retried try job too often for step(s) build

[dglazkov, 2012-09-14 21:11:34]

Will we need to add the "Disable Shadow DOM" flag back when we turn the feature
on by default?

[commit-bot: I haz the power, 2012-09-14 21:11:46]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tony@chromium.org/10917269/1

[tony, 2012-09-14 21:13:32]

On 2012/09/14 21:11:34, Dimitri Glazkov wrote:
> Will we need to add the "Disable Shadow DOM" flag back when we turn the
feature
> on by default?

I don't know. Probably not unless there's some class of security bugs that can
be solved by having such a flag (like for disabling images or disabling
plugins).

[commit-bot: I haz the power, 2012-09-14 21:14:12]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tony@chromium.org/10917269/1

[commit-bot: I haz the power, 2012-09-14 21:29:20]

Retried try job too often for step(s) build

[commit-bot: I haz the power, 2012-09-14 21:31:36]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tony@chromium.org/10917269/13002

[commit-bot: I haz the power, 2012-09-15 17:39:07]

Commit queue patch verification failed without an error message.
Something went wrong, probably a crash, a hickup or simply
the monkeys went out for dinner.
Ping the relevant dude on a on-needed basis.

[commit-bot: I haz the power, 2012-09-15 17:40:44]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tony@chromium.org/10917269/13002

[commit-bot: I haz the power, 2012-09-15 20:20:08]

Change committed as 157014