Fix accessibility order of Android tabstrip

build/android/AndroidManifest.xml

Index: build/android/AndroidManifest.xml
diff --git a/build/android/AndroidManifest.xml b/build/android/AndroidManifest.xml
index e1e2904f9d0a9607ab5bec319e5e9b216f34645f..9680c0efa66b19e478e6fa7ee995d2531c593d42 100644
--- a/build/android/AndroidManifest.xml
+++ b/build/android/AndroidManifest.xml
@@ -13,7 +13,7 @@
      be kept up-to-date.
 -->
 <manifest xmlns:android="http://schemas.android.com/apk/res/android"
-    package="dummy.package">
+    package="org.chromium.chrome">

[jbudorick, 2016/04/05 13:26:54]

What's the motivation here? It's not obvious from your gyp/gn changes why this
was necessary, and if you need a particular package name here, then this is
liable to break for other targets.

[kraush, 2016/04/05 15:48:04]

This is the package the R.java this Manifest is used for will be generated in.
You are right - as soon as there is a second user of this Manifest for R
generation, the package will no longer work (apk's have their own Manifests, but
JUnit tests for something else than ChromePublic could run into this issue)

Would you prefer me to change it to replace the file with a jinja template (with
a package parameter) instead to prevent such future problems?

[jbudorick, 2016/04/05 15:52:03]

Yeah, that'd be great.

[kraush, 2016/04/05 18:57:47]

I just looked into this some more and just realized that a mechanism for this
already exists (which will effectively use a different Manifest)
I'll update the CL using the "custom_package" attribute rather than modifying
the Manifest.

 
     <uses-sdk android:minSdkVersion="16" android:targetSdkVersion="23" />