Properly prioritize the sources of an accessible name on Android.

content/test/data/accessibility/button-name-calc-expected-android.txt

Index: content/test/data/accessibility/button-name-calc-expected-android.txt
diff --git a/content/test/data/accessibility/button-name-calc-expected-android.txt b/content/test/data/accessibility/button-name-calc-expected-android.txt
index 43e761e10db133b338d1ab017d2d9f1191fa7d32..42c013cff4df0a7963874f4864a3576ebe38c883 100644
--- a/content/test/data/accessibility/button-name-calc-expected-android.txt
+++ b/content/test/data/accessibility/button-name-calc-expected-android.txt
@@ -1,9 +1,8 @@
-#<skip - this is definitely wrong
 android.webkit.WebView focusable focused scrollable
     android.view.View
         android.widget.Button clickable focusable name='InnerText0'
-        android.widget.Button clickable focusable name='InnerText1'
-        android.widget.Button clickable focusable name='InnerText2'
-        android.widget.Button clickable focusable name='InnerText3'
-        android.widget.Button clickable focusable name='InnerText4'
-        android.widget.Button clickable focusable name='InnerText5'
+        android.widget.Button clickable focusable name='Title1'
+        android.widget.Button clickable focusable name='AriaLabel2'
+        android.widget.Button clickable focusable name='LabelledBy3'
+        android.widget.Button clickable focusable name='LabelledBy4'

[aboxhall, 2014/05/30 21:26:21]

I'm confused by this: it looks like description takes precedence, but I see this
element has aria-describedby. How does that work?

[dmazzoni, 2014/05/30 22:03:33]

Dumb luck? I think the behavior is right (labelledby is more important than
describedby if we have to pick one), and the reason it works is because Blink is
doing the right thing. What we should really do soon is have Blink try to do
less logic and just expose the underlying names, then implement the platform
logic here more clearly.

+        android.widget.Button clickable focusable name='DescribedBy5'