Remove the legacy fullscreen video path in Android.

Remove the legacy fullscreen video path in Android.

Remove the legacy fullscreen video path that was used before
html5 video controls were introduced. The last user was the
WebView, but this has been migrated to html5 controls now.

Committed: https://crrev.com/62f3270dc28a7bccc7820ea9fb51f18fd4c74f6e
Cr-Commit-Position: refs/heads/master@{#296935}

[Ignacio Solla, 2014-09-23 14:24:48]

igsolla@chromium.org changed reviewers:
+ jam@chromium.org, mkosiba@chromium.org

[Ignacio Solla, 2014-09-23 14:24:49]

mkosiba@chromium.org: Please review changes in android_webview/

jam@chromium.org: Please review changes in content/ and chrome/

[mkosiba (inactive), 2014-09-24 15:38:31]

lgtm

https://codereview.chromium.org/597523003/diff/1/content/browser/android/cont...
File content/browser/android/content_video_view.cc (left):

https://codereview.chromium.org/597523003/diff/1/content/browser/android/cont...
content/browser/android/content_video_view.cc:274: "Playing video").Pass();
intentional? how does the fullscreen html5 video view prevent the screen from
going off?

[Ignacio Solla, 2014-09-25 09:36:16]

https://codereview.chromium.org/597523003/diff/1/content/browser/android/cont...
File content/browser/android/content_video_view.cc (left):

https://codereview.chromium.org/597523003/diff/1/content/browser/android/cont...
content/browser/android/content_video_view.cc:274: "Playing video").Pass();
On 2014/09/24 15:38:30, mkosiba wrote:
> intentional? how does the fullscreen html5 video view prevent the screen from
> going off?

Good catch, there is a bug that we didn't notice, crbug/417623. Having the
screen always on in developer settings has its disadvantages :( We can't remove
this for the WebView, so I will fix it in a separate change that I will submit
before this change, and then I will rebase.

[Ignacio Solla, 2014-09-25 12:44:15]

Applying the patch fails because I assume that I need to land the base patch
first. You should still be able to review though.

[jam, 2014-09-25 22:44:27]

lgtm

[Ignacio Solla, 2014-09-26 12:43:06]

The CQ bit was checked by igsolla@chromium.org

[commit-bot: I haz the power, 2014-09-26 12:43:24]

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

[commit-bot: I haz the power, 2014-09-26 12:46:31]

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

[commit-bot: I haz the power, 2014-09-26 12:46:32]

Try jobs failed on following builders:
  mac_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu/builds/61185)
  ios_dbg_simulator on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_dbg_simulator...)
  ios_rel_device on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device/bu...)
  ios_rel_device_ninja on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device_ni...)
  mac_chromium_compile_dbg on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
  mac_chromium_rel_swarming on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
  win8_chromium_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win8_chromium_rel...)

[Ignacio Solla, 2014-09-26 13:05:36]

The CQ bit was checked by igsolla@chromium.org

[commit-bot: I haz the power, 2014-09-26 13:06:05]

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

[commit-bot: I haz the power, 2014-09-26 14:20:49]

Committed patchset #5 (id:80001) as e81bc186691a2810a0eca99b607ad22fe7ddee69

[commit-bot: I haz the power, 2014-09-26 14:21:27]

Patchset 5 (id:??) landed as
https://crrev.com/62f3270dc28a7bccc7820ea9fb51f18fd4c74f6e
Cr-Commit-Position: refs/heads/master@{#296935}