Use ScopedTaskEnvironment instead of MessageLoopForUI in content tests.

Use ScopedTaskEnvironment instead of MessageLoopForUI in content tests.

ScopedTaskEnvironment allows usage of ThreadTaskRunnerHandle and
base/task_scheduler/post_task.h within its scope. It should be
instantiated in everytest that uses either of these APIs
(i.e. no test should instantiate a MessageLoop directly).

Motivation for ScopedTaskEnvironment can be found in:
https://docs.google.com/document/d/1QabRo8c7D9LsYY3cEcaPQbOCLo8Tu-6VLykYXyl3Pkk/edit

BUG=708584
R=gab@chromium.org
TBR=emircan@chromium.org, tdresser@chromium.org

Review-Url: https://codereview.chromium.org/2846933002
Cr-Commit-Position: refs/heads/master@{#468368}
Committed: https://chromium.googlesource.com/chromium/src/+/8f9f016285a1178e63e8676ecc950db84a92cc65

[fdoray, 2017-04-27 18:30:38]

The CQ bit was checked by fdoray@chromium.org to run a CQ dry run

[fdoray, 2017-04-27 18:30:40]

gab@: PTAL

The change will then be TBRed to the owner.

[commit-bot: I haz the power, 2017-04-27 18:31:19]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-27 18:44:17]

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

[commit-bot: I haz the power, 2017-04-27 18:44:18]

Dry run: Try jobs failed on following builders:
  android_compile_dbg on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_comp...)

[fdoray, 2017-04-27 19:08:04]

The CQ bit was checked by fdoray@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-27 19:09:07]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-27 19:34:26]

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

[commit-bot: I haz the power, 2017-04-27 19:34:27]

Dry run: Try jobs failed on following builders:
  android_compile_dbg on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_comp...)
  android_n5x_swarming_rel on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_...)
  linux_chromium_tsan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[emircan, 2017-04-27 22:16:08]

content/renderer/* lgtm

[fdoray, 2017-04-28 13:50:37]

The CQ bit was checked by fdoray@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-28 13:51:10]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-28 14:09:36]

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

[commit-bot: I haz the power, 2017-04-28 14:09:37]

Dry run: This issue passed the CQ dry run.

[gab, 2017-05-01 18:16:13]

content/browser lgtm

[fdoray, 2017-05-01 18:16:31]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2017-05-01 18:16:59]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-01 18:47:39]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1493662591379220,
"parent_rev": "4f731454df3bdd7076668f4c906dc1eaab38e8ad", "commit_rev":
"8f9f016285a1178e63e8676ecc950db84a92cc65"}

[commit-bot: I haz the power, 2017-05-01 18:47:46]

Description was changed from

==========
Use ScopedTaskEnvironment instead of MessageLoopForUI in content tests.

ScopedTaskEnvironment allows usage of ThreadTaskRunnerHandle and
base/task_scheduler/post_task.h within its scope. It should be
instantiated in everytest that uses either of these APIs
(i.e. no test should instantiate a MessageLoop directly).

Motivation for ScopedTaskEnvironment can be found in:
https://docs.google.com/document/d/1QabRo8c7D9LsYY3cEcaPQbOCLo8Tu-6VLykYXyl3P...

BUG=708584
R=gab@chromium.org
TBR=emircan@chromium.org, tdresser@chromium.org
==========

to

==========
Use ScopedTaskEnvironment instead of MessageLoopForUI in content tests.

ScopedTaskEnvironment allows usage of ThreadTaskRunnerHandle and
base/task_scheduler/post_task.h within its scope. It should be
instantiated in everytest that uses either of these APIs
(i.e. no test should instantiate a MessageLoop directly).

Motivation for ScopedTaskEnvironment can be found in:
https://docs.google.com/document/d/1QabRo8c7D9LsYY3cEcaPQbOCLo8Tu-6VLykYXyl3P...

BUG=708584
R=gab@chromium.org
TBR=emircan@chromium.org, tdresser@chromium.org

Review-Url: https://codereview.chromium.org/2846933002
Cr-Commit-Position: refs/heads/master@{#468368}
Committed:
https://chromium.googlesource.com/chromium/src/+/8f9f016285a1178e63e8676ecc95...
==========

[commit-bot: I haz the power, 2017-05-01 18:47:47]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/8f9f016285a1178e63e8676ecc95...