Android 4.1 with Chrome - Select on footer with data-position="fixed" no response #5140

Closed
dandawong opened this Issue Oct 8, 2012 · 3 comments

Projects

None yet

3 participants

@dandawong

When i use Android 4.1 with Chrome to test the page with select box on a fixed position footer, the select box just has no response when i tap the screen and toggle the visibility of the fixed footer, here is the test page:

http://jsbin.com/iyenuv/1/

I also test it with the original browser and firefox on Android 4.1, which has no problem, also the device i use to test is Galaxy Nexus.

@jaspermdegroot
jQuery Foundation member

@dandawong

Thanks for reporting the issue.

The cause of it is exactly the same as #4663. On Chrome for Android overflow: hidden; in a fixed toolbar makes buttons unresponsive when you scroll the page.

In this case we use overflow: hidden; for .ui-select .ui-btn. We have to see if we can do without that without causing other issues.

We also have to test if this Chrome bug is causing issues when using ui-grid or ui-bar in fixed toolbars because those classes have overflow set to hidden as well.

@dandawong

After override the overflow: hidden; for .ui-select .ui-btn to overflow: visible !important;, it does fix the problem when the page first load, but after tap the screen and toggle the toolbar, the select box become no response, finally i found that if you also override the -webkit-transform: translateY(0); to -webkit-transform: inherit !important; for .slideup.in, it work for the issue.

Here is the css and the test page http://jsbin.com/iyenuv/3

.ui-select {
  overflow: visible !important;
}
.ui-btn {
  overflow: visible !important;
}
.slideup.in {
    -webkit-transform: inherit !important;
}
@Wilto Wilto was assigned Oct 15, 2012
@Wilto

Dibs. Looking into this now.

@Wilto Wilto added a commit that closed this issue Oct 16, 2012
@Wilto Wilto Fixes #5140 - Select menus inside elements in Android 4.1 Chrome now …
…work after scrolling.
67e6fbc
@Wilto Wilto closed this in 67e6fbc Oct 16, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment