Open GoogleCodeExporter opened 9 years ago
I am experiencing the same. just upgraded DroidX motorola phone to latest OS
version 2.3.15... select elements on non iUi pages working ok. not working
in my app nor on music demo theme switcher.
Original comment by kurt.rob...@gtempaccount.com
on 28 Sep 2010 at 10:32
To be honest as I didn't investigate this issue further after reporting it as I
did not continue devlopment using IUI
Original comment by patrick....@gmail.com
on 28 Sep 2010 at 11:07
I'm also seeing this bug. Drop downs (ie <SELECT>) work fine in every browser
except Android 1.6 or 2.x. I'm attaching a screen shot showing this.
Problem is likely CSS, as dropdowns do work on other sites in Android. Also,
problem persists even when including just the iui.css and not using the
javascript code at all.
This is the only major bug I experienced with IUI and Android. I have a bunch
of small visual tweaks and small bug fixes I had to make to get it working
perfectly. I'll be posting an issue entry on that, and my own patches.
-john
Original comment by magnat...@gmail.com
on 25 Nov 2010 at 3:10
Attachments:
I am seeing same issue.
"Dropdown does not work on mobile device running android 1.6 or 2.X"
However it worked on a device running android 1.5
I have checked CSS and found 'opacity' property which specifies the
transparency of an element on my web page is the cause of disabled dropdown on
android phone. When i remove 'opacity' from my CSS, the dropdown works fine on
all android devices.
However, on my website, there are a couple of other pages which has 'Opacity'
property in CSS and a drop down works fine. I doubt the 'location' of the drop
down on my all pages.
Here is what i did for a test case:
1: Create Dropdowns at design-time and run-time with CSS having opacity
property.
- Result: 3/4 drop downs do not work
2: Change position of the dropdown ( Create a <Table> and move the dropdowns a
little upper or lower side.
- Result: 2/4 dropdown work.
3: Remove 'Opacity' property from my CSS.
- Result: 4/4 dropdowns work fine
At this time, it seems ,
"Eventhough android default browser and Dolphin HD browser supports 'Opacity'
property in CSS, it creates issue for Dropdown when the Dropdown is placed at
some specific location on the web page.
This behavior could be because, android browser creates effect similar to
modal-pop when dropdown is clicked. The popup panel is transperent at border
area showing rest of the browser contents. The browser itself uses 'opacity'
which might be conflicting with web page opacity and dropdown click event
handler"
Anyone having similar issue, please spread some light.!
Thank you,
Cinni
Original comment by sweetcie...@gmail.com
on 8 Dec 2010 at 6:13
Hi,
I have a similar problem:
I created a mobile version of a website with a Joomla! - Plugin called Joomla
Mobile.
All the select elements(DropDown-Menus) work fine in the desktop version of the
site, but in the mobile version they just don´t work (HTC Evo, Android 2.3.3).
They just do nothing. The select elements I use in the Desktop version are
exactly the same (same php-script that produces them) as in the mobile version.
- I checked my CSS, i do NOT use the opacity property.
- In the android emulators, everything works. On the phone it just doesn´t
work.
I don´t know what more to try, any suggestions?
Original comment by kastenmi...@gmail.com
on 19 Jul 2011 at 9:37
Hi I am also facing the same issue(All the select elements(DropDown-Menus) work
fine in the desktop version of the site and in iphone, but in the mobile
version they just don´t work (HTC Evo, Android). can anybody help me out ?
Original comment by chakrira...@gmail.com
on 26 Jul 2011 at 7:11
I'm getting the same behaviour - select drop down boxes do not drop down with
an Android mobile browser
Original comment by vinoma...@gmail.com
on 27 Jan 2012 at 8:17
Could you try it with the latest release 0.40-beta2? It's on the downloads
page:
http://code.google.com/p/iui/downloads/list
and also running on GAE here:
http://demo.iui-js.org/
Original comment by msgilli...@gmail.com
on 27 Jan 2012 at 8:22
Thanks - seems to work using the Android SDK emulator. Will have to try again
Monday using an actual device.
Original comment by vinoma...@gmail.com
on 27 Jan 2012 at 11:18
Could someone please test this URL on a real device?
http://goo.gl/EajkV
Thx
Original comment by remi.gru...@gmail.com
on 27 Jan 2012 at 2:13
[deleted comment]
Tested this morning
Works as it should in the fieldset, but NOT in a panel or a div
Original comment by vinoma...@gmail.com
on 5 Feb 2012 at 10:59
Well, the good news is: it doesn't work neither here using emulator with
Android 2.2. Good news since it helps to find a solution.
Could you please confirm what i see here on your real device, that using 0.5
alpha1 it all works?
http://we-are-gurus.com/labs/iui/issues/263/?v=0.5a1
Then i'll look at what i did solve in this new code :)
Original comment by remi.gru...@gmail.com
on 6 Feb 2012 at 12:21
yeah this is working
Original comment by denisndw...@gmail.com
on 7 Feb 2012 at 9:09
[deleted comment]
Can anyone explain what fixed this problem? I am using an ANCIENT modified
version of IUI and this is a major issue for me. What changes can I apply to
my old IUI to resolve it? (I so hope there is a simple answer...).
If anyone would like to see the app, its at x-snightlife.com. just choose an
event and hit the RSVP button. the number of guests dropdown does not open on
Droid.
Thanks!
Kurt
Original comment by kurt.rob...@gmail.com
on 15 May 2012 at 4:47
EUREKA! I found a solution that works in my old IUI Version 0.40-dev2. it
seems that if the select element is inside of an element with .data class
like td.data, then an iui css rule which assigns position: relative applies
and that seems to make the select element pop up normally. I actually tried
to assign position: relative; directly to the select element but it did not fix
the problem so I'm not sure what is really causing the change but this solution
is good enough for me till I upgrade
Original comment by kurt.rob...@gmail.com
on 24 Jun 2012 at 2:37
Is there still an issue in 0.4-beta3 or should I close this bug?
Original comment by msgilli...@gmail.com
on 27 Jun 2012 at 10:06
Original issue reported on code.google.com by
patrick....@gmail.com
on 23 Jul 2010 at 8:55