Support a runtime flag for navigator content utils feature

Support a runtime flag for navigator content utils feature

Add a runtime flag for navigator content utils feature. This patch exposes in the public API
so that they can be toggled.

BUG= N/A

[gyuyoung-inactive, 2013-08-18 05:09:54]

Add abarth to reviewers.

[abarth-chromium, 2013-08-19 19:18:07]

https://codereview.chromium.org/22855008/diff/1/Source/core/page/RuntimeEnabl...
File Source/core/page/RuntimeEnabledFeatures.in (right):

https://codereview.chromium.org/22855008/diff/1/Source/core/page/RuntimeEnabl...
Source/core/page/RuntimeEnabledFeatures.in:64: NavigatorContentUtils
status=stable
Show they be turned on in stable?  If so, we don't need to add a runtime flag
because no one is interested in disabling the feature.  Perhaps you meant
"experimental" ?

https://codereview.chromium.org/22855008/diff/1/public/web/WebRuntimeFeatures.h
File public/web/WebRuntimeFeatures.h (right):

https://codereview.chromium.org/22855008/diff/1/public/web/WebRuntimeFeatures...
public/web/WebRuntimeFeatures.h:141: WEBKIT_EXPORT static bool
isNavigatorContentUtilsEnabled();
There's no need for this API.  We can control the feature with the generic
test/experimental/stable API.

[gyuyoung-inactive, 2013-08-20 08:24:36]

https://codereview.chromium.org/22855008/diff/1/Source/core/page/RuntimeEnabl...
File Source/core/page/RuntimeEnabledFeatures.in (right):

https://codereview.chromium.org/22855008/diff/1/Source/core/page/RuntimeEnabl...
Source/core/page/RuntimeEnabledFeatures.in:64: NavigatorContentUtils
status=stable
On 2013/08/19 19:18:07, abarth wrote:
> Show they be turned on in stable?  If so, we don't need to add a runtime flag
> because no one is interested in disabling the feature.  Perhaps you meant
> "experimental" ?

If I don't need to add *stable* feature, I would like to close this cl.

https://codereview.chromium.org/22855008/diff/1/public/web/WebRuntimeFeatures.h
File public/web/WebRuntimeFeatures.h (right):

https://codereview.chromium.org/22855008/diff/1/public/web/WebRuntimeFeatures...
public/web/WebRuntimeFeatures.h:141: WEBKIT_EXPORT static bool
isNavigatorContentUtilsEnabled();
On 2013/08/19 19:18:07, abarth wrote:
> There's no need for this API.  We can control the feature with the generic
> test/experimental/stable API.

I don't understand well. Stable APIs as Geolocation, MediaStream were added to
here. Could you let me know what is difference ?

[abarth-chromium, 2013-08-20 19:22:27]

On 2013/08/20 08:24:36, gyuyoung wrote:
> I don't understand well. Stable APIs as Geolocation, MediaStream were added to
> here. Could you let me know what is difference ?

They weren't stable when the flags were created.  We should probably remove the
flags.  We don't need the ability to disable the features anymore.

[gyuyoung-inactive, 2013-08-21 01:36:02]

On 2013/08/20 19:22:27, abarth wrote:
> On 2013/08/20 08:24:36, gyuyoung wrote:
> > I don't understand well. Stable APIs as Geolocation, MediaStream were added
to
> > here. Could you let me know what is difference ?
> 
> They weren't stable when the flags were created.  We should probably remove
the
> flags.  We don't need the ability to disable the features anymore.

Ok, If so, I would like to close this issue. When I have time, I will suggest
this issue on blink-dev. Thanks.