Add enabling/disabling of NetworkInformation API via WebRuntimeFeatures.

Add enabling/disabling of NetworkInformation API via WebRuntimeFeatures.  This lets us restrict the API to the platforms that are fully implemented while we develop the others.

See https://codereview.chromium.org/424823002/ for the Chromium code that uses this.

BUG=368358
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=179147

[jkarlin, 2014-07-28 17:01:38]

jochen: Please review all, and thanks!

[jkarlin, 2014-07-29 11:21:05]

On 2014/07/28 17:01:38, jkarlin wrote:
> jochen: Please review all, and thanks!

Ping? Thanks jochen!

[Peter Beverloo, 2014-07-29 11:24:34]

On 2014/07/29 11:21:05, jkarlin wrote:
> On 2014/07/28 17:01:38, jkarlin wrote:
> > jochen: Please review all, and thanks!
> 
> Ping? Thanks jochen!

It would help if you'd explain why this is necessary, since neither the
description nor the bug makes mention of this.

NetworkInformation in RuntimeEnabledFeatures.in is defined as
status=experimental, when we ship features we usually change that to
status=stable, without needing to change anything on the Chromium side.

I suspect that this may have to do with only shipping the feature on certain
platforms. Mentioning that in the CL description would provide good context.
(The API Owners are meeting today to discuss this issue, afaik.)

[jochen (gone - plz use gerrit), 2014-07-29 11:24:47]

lgtm

[jochen (gone - plz use gerrit), 2014-07-29 11:25:18]

(but yes, explaining why you need this would help)

[jkarlin, 2014-07-29 11:29:20]

On 2014/07/29 11:24:34, Peter Beverloo wrote:
> On 2014/07/29 11:21:05, jkarlin wrote:
> > On 2014/07/28 17:01:38, jkarlin wrote:
> > > jochen: Please review all, and thanks!
> > 
> > Ping? Thanks jochen!
> 
> It would help if you'd explain why this is necessary, since neither the
> description nor the bug makes mention of this.
> 
> NetworkInformation in RuntimeEnabledFeatures.in is defined as
> status=experimental, when we ship features we usually change that to
> status=stable, without needing to change anything on the Chromium side.
> 
> I suspect that this may have to do with only shipping the feature on certain
> platforms. Mentioning that in the CL description would provide good context.
> (The API Owners are meeting today to discuss this issue, afaik.)

Yes, thanks for pointing that out.  The description is now updated.

[jkarlin, 2014-07-29 11:30:36]

The CQ bit was checked by jkarlin@chromium.org

[commit-bot: I haz the power, 2014-07-29 11:31:37]

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

[commit-bot: I haz the power, 2014-07-29 12:22:50]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_blink_rel on tryserver.blink
(http://build.chromium.org/p/tryserver.blink/builders/win_blink_rel/builds/19441)

[commit-bot: I haz the power, 2014-07-29 13:49:23]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-07-29 13:49:24]

Try jobs failed on following builders:
  win_blink_rel on tryserver.blink
(http://build.chromium.org/p/tryserver.blink/builders/win_blink_rel/builds/19441)

[jkarlin, 2014-07-29 14:40:57]

The CQ bit was checked by jkarlin@chromium.org

[commit-bot: I haz the power, 2014-07-29 14:41:53]

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

[commit-bot: I haz the power, 2014-07-29 14:43:18]

Change committed as 179147