My current jQM project has two "notext" link buttons side-by-side in a fixed header bar. This wasn't a problem in 1.0.1, but the true fixed positioning in 1.1 has lead to a problem in the Android 2.2 browser. The first of the two buttons is usable, but the second one gets its active state triggered without actually causing navigation to the new page.
My fix works by eliminating all relative or absolute positioning in the buttons and hiding the button text with a modified version of the "font crunch" approach used in the HTML5 Boilerplate and discussed in jQM issue #3851.
So far I've tested the fix in these browsers:
It seems likely this issue is a subset of the larger problems with absolute positioning in Android 2.2 and 2.3 discovered in @Wilto's research into issue #3712. Might the approach taken in my fix for this issue help with other, related absolute positioning problems?
#4625 has been closed as duplicate. The issue is the same and also on Android 2.2, but it only happens with PG.
@uGoMobi @toddparker This is 7 months stale tested with latest on jsbin provided on HTC Thunderbolt 2.3.7 and several 2.3 on browser stack and can no longer reproduce unless @adammessinger can still reproduce this i would close as fixed.
@arschmitz - It's a Android 2.2 issue.
I checked this with the latest jQuery Mobile http://jsbin.com/acIRUBo/60 and it is still and issue on Android 2.2. I did however want to add a bit more detail. The active state is indeed added on the first touch with no navigation, but on a subsequent touch it does result in navigation. Also of note: clicking on the simulator worked but touching on the touchscreen resulted in the behavior described. Tested with Android 2.2 simulator.
I wasn't able to reproduce this on an Android 2.3 emulator. The Genymotion utility doesn't allow me to choose a 2.2 device to test. I was able to test on BrowserStack on a 2.2 device but I also wasn't able to reproduce. See video here: https://www.youtube.com/watch?v=yyKIVcyie60&feature=youtube_gdata_player No doubt that you guys were able to reproduce @jaspermdegroot & @cgack but unable to do so on my end to help debug.
@ldeluca we no longer officially support android 2.2 so im going to close this as wont fix