We have the latest JQM, Jquery. We have a settings page with 6 select boxes on and a fixed footer with 4 buttons.
If you scroll so that 1 of the select boxes is underneath the footer and then select a button, instead of the default behavior of going to the href contained within the footer button, our Galaxy Tab and Galaxy S2 (Android 2.2 - Froyo/GingerBread) open the native select box options. This is not happening in Chrome on the desktop or any apple device.
I have a good go at messing with the z-index of the footer to make it on top (it is visually) etc but nothing is working.
Can you post a test page using latest? Template: http://jsbin.com/omuqas/edit
I have done that , I think, there is a test page in the jsbin now.
Closed by mistake.
@harvo - you need to hit the "Save" button in JSbin, then copy the URL to the page and paste here.
Guessing it's this:
In this it?
Yes or now it's http://jsbin.com/omuqas/12/edit due to my over enthusiastic button pressing, thanks.
#4241 sounds similar to this
It is, thanks. I can see that the issue has been spotted and added to the 1.1.1 milestones, thanks !
Hi Harvo -
I just tested this on a 2.2 and 2.3 device and the footer links seem to be working ok but I've heard that others have run into this too. Seems like a "sometimes" kind of Android bug.
On your test page, none of the selects open. Android is really buggy with fixed and it frequently can break select menus with fixed and other CSS properties are combined but since this page is pretty much stock styles, that seems odd. Since the selects work fine on this docs page with fixed toolbars (scroll down for the form), I'm wondering if things are a bit off because you don't have labels associated with each select. The scripts are picky about semantics because they are used for config.
@harvo - Yep, you'll find Android to be very buggy but in very inconsistent ways. Some people will report an issue but it can't be reproduced on the same version (ex. 2.3.5), only within a certain model or OEM. The CSS is very fragile and can cause all sorts of issues with scrolling, transitions, fixed positioning, select menu operation, etc. We do our best, but at a certain point, some things are hard to fix because we're just writing code with web standards so if a browser has a badly broken implementation of a feature, the best we can do is shield the code or style from them.
@harvo - I am closing this ticket as a duplicate of #3912.
I am facing the same issue, can you please let me know any one able to solve this problem.