You can clone with
Non-native selects that are disabled by default become native when enabled progammatically, while if they are not disabled by default, then disabled programmatically and enabled again, they remain non-native.
I have created the jsfiddle below to illustrate:http://jsfiddle.net/4BBBb/31/
This is a duplicate of #3889, but I have updated the the jsfiddle for clarity
I can confirm on chrome. Working on a fix now.
disabled custom selects will now enhance Fixes #3894
Thanks John. #3889 can also be closed as was the same issue.
@johnbender If you look at my jsfiddle, now something really strange happens: press the button to enable the second select (the non-native), then press the select. The options appear but with a dark grey layer and it is not possible to choose an option. I am on the iPad with iOS 4.3.3
Hrm I only have the 5.1 emulators. Does it work outside of the fiddle iframe?
Here are some screen shots:http://users.cscs.wmin.ac.uk/~coloma/jqm/select1.png (the 2nd select that becomes enabled, but it looks like the options aren't).
This is what it should look like (the 3rd select) http://users.cscs.wmin.ac.uk/~coloma/jqm/select2.png
I have the feeling the select gets enabled and keeps its non-native 'status' but it looks like the options aren't enabled. Would it be simply a matter of enabling the select and its children?
What is also strange is that the native version is all properly enabled:http://users.cscs.wmin.ac.uk/~coloma/jqm/select3.png