Remove Gamepad runtime flag (status=stable) for chromium

Remove Gamepad runtime flag (status=stable) for chromium

BUG=402536
Committed: https://crrev.com/231e285c50ae938b239db144975112dbe13e640d
Cr-Commit-Position: refs/heads/master@{#296660}

[heeyoun.lee, 2014-09-19 08:57:23]

heeyoun.lee@samsung.com changed reviewers:
+ avi@chromium.org

[heeyoun.lee, 2014-09-19 08:57:24]

This is for chromium. PTAL

blink : https://codereview.chromium.org/582363002/

[Avi (use Gerrit), 2014-09-20 01:09:18]

lgtm

[heeyoun.lee, 2014-09-22 04:51:05]

The CQ bit was checked by heeyoun.lee@samsung.com

[commit-bot: I haz the power, 2014-09-22 04:51:44]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/580403003/1

[heeyoun.lee, 2014-09-22 04:52:46]

The CQ bit was unchecked by heeyoun.lee@samsung.com

[heeyoun.lee, 2014-09-25 05:54:11]

The CQ bit was checked by heeyoun.lee@samsung.com

[commit-bot: I haz the power, 2014-09-25 05:55:00]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/580403003/1

[commit-bot: I haz the power, 2014-09-25 05:55:51]

Committed patchset #1 (id:1) as aa50476305f74c67b850b0a5bbcfe1c3120cf9d3

[commit-bot: I haz the power, 2014-09-25 05:56:29]

Patchset 1 (id:??) landed as
https://crrev.com/231e285c50ae938b239db144975112dbe13e640d
Cr-Commit-Position: refs/heads/master@{#296660}

[kbalazs, 2014-10-07 18:30:46]

On 2014/09/25 05:56:29, I haz the power (commit-bot) wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/231e285c50ae938b239db144975112dbe13e640d
> Cr-Commit-Position: refs/heads/master@{#296660}

Hey guys, this will not work. I believe it will cause us to expose the gamepad
api but it will not work, because it relies on 4.4 api's. So actually it will
result in a crash (unexistent function java exception).

[kbalazs, 2014-10-07 20:35:34]

On 2014/10/07 18:30:46, kbalazs wrote:
> On 2014/09/25 05:56:29, I haz the power (commit-bot) wrote:
> > Patchset 1 (id:??) landed as
> > https://crrev.com/231e285c50ae938b239db144975112dbe13e640d
> > Cr-Commit-Position: refs/heads/master@{#296660}
> 
> Hey guys, this will not work. I believe it will cause us to expose the gamepad
> api but it will not work, because it relies on 4.4 api's. So actually it will
> result in a crash (unexistent function java exception).

Revising my standpoint (and not). It won't crash, just doesn't work. But than we
should not expose the js api if the feature doesn't work.

[kbalazs, 2014-10-07 20:48:36]

On 2014/10/07 20:35:34, kbalazs wrote:
> On 2014/10/07 18:30:46, kbalazs wrote:
> > On 2014/09/25 05:56:29, I haz the power (commit-bot) wrote:
> > > Patchset 1 (id:??) landed as
> > > https://crrev.com/231e285c50ae938b239db144975112dbe13e640d
> > > Cr-Commit-Position: refs/heads/master@{#296660}
> > 
> > Hey guys, this will not work. I believe it will cause us to expose the
gamepad
> > api but it will not work, because it relies on 4.4 api's. So actually it
will
> > result in a crash (unexistent function java exception).
> 
> Revising my standpoint (and not). It won't crash, just doesn't work. But than
we
> should not expose the js api if the feature doesn't work.

Now I change my mind...

[16:42] <jamesr__> won't it just return an empty list of gamepads?
[16:43] <kbalazs> jamesr__: yes, I think it will do that. hm, maybe I'm too
paranoid.
[16:44] <jamesr__> sounds like working to me
[16:46] <kbalazs> jamesr__: ok, you buyed me. I was indeed too paranoic.

Sorry for the paranoia.