Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Select Boxes selected when footer button clicked Andriod 2.2/2.3 #4204

Closed
harvo opened this Issue · 17 comments

4 participants

@toddparker

Can you post a test page using latest? Template: http://jsbin.com/omuqas/edit

@harvo

Hi Todd,

I have done that , I think, there is a test page in the jsbin now.

@harvo harvo closed this
@harvo harvo reopened this
@harvo

Closed by mistake.

@toddparker

@harvo - you need to hit the "Save" button in JSbin, then copy the URL to the page and paste here.

@harvo

Yes or now it's http://jsbin.com/omuqas/12/edit due to my over enthusiastic button pressing, thanks.

@harvo
@harvo
@jaspermdegroot
Collaborator

#4241 sounds similar to this

@harvo

It is, thanks. I can see that the issue has been spotted and added to the 1.1.1 milestones, thanks !

@toddparker

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.

http://jquerymobile.com/test/docs/toolbars/bars-fixed.html

@harvo
@toddparker
@harvo
@toddparker

@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.

@jaspermdegroot
Collaborator

@harvo - I am closing this ticket as a duplicate of #3912.

@gvmuralikrish

Hi all

I am facing the same issue, can you please let me know any one able to solve this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.