At the end of all of it, if anyone asks me what I recommend for mobile/tablet web development (and they usually don't because everyone presumes the standard is pixel-perfect app-like appearance/behavior), it's simple layouts that accommodate the idea that your CSS is a suggestion and lightly enhanced interaction with not-constantly-running JS... unless the product absolutely requires some other mode of interaction.
There are a number of reasons for this, but one of them was exactly this problem with Android. During the time I was working with it I don't think we ever thoroughly cracked what signifiers would help us reliably reproduce reported issues... let alone fix them (you can detect a whiff of my desperation this time last year from this unanswered SO question: http://stackoverflow.com/questions/23142762/how-to-identify-... ).
Not my problem anymore. Last I heard the new owners are planning to rewrite with more responsive design and using angular. Should be fun.