[Android] Fix sequence of context menu in CCT is incorrect

[Android] Fix sequence of context menu in CCT is incorrect

The sequence of context menu for CCT is incorrect that "Open in
incognito tab" is shown before "Open in new Chrome tab". This is because
Chrome appends those items sequentially to the front of item list (like a
Stack). To fix the problem, append the items to the front in the opposite
direction.

BUG=725665
Review-Url: https://codereview.chromium.org/2910703002
Cr-Commit-Position: refs/heads/master@{#475151}
Committed: https://chromium.googlesource.com/chromium/src/+/ea289a66e6444098032ce8f5b3c0dc0da1923c25

[ltian, 2017-05-26 18:06:43]

ltian@chromium.org changed reviewers:
+ tedchoc@chromium.org

[ltian, 2017-05-26 18:06:44]

Can you take a look of this CL?

Thanks!

[Ted C, 2017-05-26 18:33:45]

lgtm

[ltian, 2017-05-26 19:17:44]

The CQ bit was checked by ltian@chromium.org

[commit-bot: I haz the power, 2017-05-26 19:18:17]

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-26 19:26:15]

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

[commit-bot: I haz the power, 2017-05-26 19:26:15]

Try jobs failed on following builders:
  android_arm64_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_arm6...)
  android_clang_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_clan...)
  android_compile_dbg on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_comp...)
  android_cronet on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_cron...)
  android_n5x_swarming_rel on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_...)
  cast_shell_android on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...)
  linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)
  cast_shell_linux on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/cast_shell_linu...)
  chromeos_amd64-generic_chromium_compile_only_ng on
master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_amd64-...)
  chromeos_daisy_chromium_compile_only_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_daisy_...)
  linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_compile_dbg_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_headless_rel on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_tsan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[ltian, 2017-05-26 21:12:06]

The CQ bit was checked by ltian@chromium.org

[commit-bot: I haz the power, 2017-05-26 21:12:35]

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-26 21:59:11]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1495833126402560, "parent_rev":
"ee16a4e7c79222b24844039c71708dc0042a14f2", "commit_rev":
"ea289a66e6444098032ce8f5b3c0dc0da1923c25"}

[commit-bot: I haz the power, 2017-05-26 21:59:23]

Description was changed from

==========
[Android] Fix sequence of context menu in CCT is incorrect

The sequence of context menu for CCT is incorrect that "Open in
incognito tab" is shown before "Open in new Chrome tab". This is because
Chrome appends those items sequentially to the front of item list (like a
Stack). To fix the problem, append the items to the front in the opposite
direction.

BUG=725665
==========

to

==========
[Android] Fix sequence of context menu in CCT is incorrect

The sequence of context menu for CCT is incorrect that "Open in
incognito tab" is shown before "Open in new Chrome tab". This is because
Chrome appends those items sequentially to the front of item list (like a
Stack). To fix the problem, append the items to the front in the opposite
direction.

BUG=725665

Review-Url: https://codereview.chromium.org/2910703002
Cr-Commit-Position: refs/heads/master@{#475151}
Committed:
https://chromium.googlesource.com/chromium/src/+/ea289a66e6444098032ce8f5b3c0...
==========

[commit-bot: I haz the power, 2017-05-26 21:59:24]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/ea289a66e6444098032ce8f5b3c0...