Native select Menu no event on Adroid 2.2 or above

[chenchen]

I am using select Menu with no role(native select menu), It works ok on the Android 2.1 and 1.6 devices. When i run it on the Android 2.2 device, there is no select menu pop out. It seems the select menu didn't receive events.

[davibe]

the same happens here. I don't knw what did chebchen mean by "with no role" but I'm using data-native-menu="true" . any clue ?

[w00tazn]

My Samsung Galaxy S with Samsung's Froyo has a customized native select that doesn't show up when using JQM. Haven't seen this issue on other 2.2 devices with a stock native select.

[toddparker]

I just tested this on on both our Android 2.2 devices (HTC Incredible and Droid) and both the 100% native selects (data-role="none") and the native menu selects (data-native-menu="true") both work fine. Can you re-test on the latest:

native select:
http://jquerymobile.com/test/docs/forms/forms-all-native.html

native menu:
http://jquerymobile.com/test/docs/forms/forms-selects.html

Cheers,
Todd

[chenchen]

It works, Thanks

[blq]

This needs to be reopened.
I've tested today's "test" pages on HTC Desire, HTC Legend, Samsung Galaxy Tab.
I notice that almost always the native select menus don't work when transitioning to the page with the select menu. But if you reload the same page it works. I.e seems to be some timing issue(?) ajax, page cache? RC1 seems to work, can't reproduce currently.

(bunch of similar issues it seems, #897, #1830, #1051 etc).

[argyleink]

build is using "latest" syntax for jquery mobile builds: Device Android G2 running 2.3

• visited 2 test pages for selects with no native select menu showing
• my select menu's dont live on a "transition to" page, the page is the first landing page of the app, no page cache.
• setting opacity in css didnt fix the bug.
• setting data-role to none doesnt fix issue, when tapped it has no reaction
• the select appears to be in focus/highlighting but the menu options arent visible (when data-role is NOT set to none)
• tried many menu items and a couple menu items, no change

i'm especially concerned with this one since i was able to use native menu selects a few weeks ago. my form is considerably more intense now, but my phone didnt pop the select menu options in the test pages supplied either

[argyleink]

FIXED with just CSS!

.ui-page { -webkit-backface-visibility:visible !important; }

[toddparker]

Are you able to reproduce this on my docs page links above in 2.2?
The backface trick may help, but uses a lot of memory so the browser could get unstable. Seems that that this would fix things.

[argyleink]

sorry i should have been more specific, i tested the above solution on a G2 with 2.3. i can't say if it's a solution to 2.2

[jumpinjackie]

I too am experiencing un-usable native select menus. I'm using stock Android Gingerbread browser (2.3) on a Nexus One

Even the native menus on the 1.0RC2 demo page (http://jquerymobile.com/demos/1.0b2/docs/forms/selects/index.html) do not work.

[johnbender]

@jumpinjackie

I think you meant to link to latest. But either way I can reproduce.

@toddparker @Wilto

Bisect points to be7f74262b2c32f1d30d0497cf5f63bdeb23dc18. No clue why that causes the problem but if you checkout the commit before it works, and the commit after it's broken.

[edit] and now I'm going to sleep.

[jumpinjackie]

select menus are still fubar on Android even with this fix.

The only cases where select menus will work at the moment are it is fully native (data-role="none" and un-styled by JQM) or it uses a custom menu (which is horribly slow on Android).

The default styled select with native menu options still does not work.

Look at these pages:

http://jquerymobile.com/test/docs/forms/forms-all.html

http://jquerymobile.com/test/docs/forms/selects/

Tap any select menu on these pages that doesn't have custom menu options. They still do nothing.

I am using the stock Android gingerbread (2.3) browser on a Nexus One. The same behaviour can be observed through the Gingerbread emulator.

Another data point to add is that this was working in 1.0 RC1. Whatever broke this was committed after RC1.