You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 29, 2017. It is now read-only.
I have tested this many times on many devices (Nexus 7, Nexus 5, Samsung Galaxy S4/S3, etc..) and I notice that top buttons (menu, back, etc) on Android are quite unresponsive.
I have tried several ways to resolve the issue, like assigning touchEnabled=false to the children images, but nothing worked so far.
I'm using the master branch for testing purposes, using the devices mentioned above, most of them running Android 4.x. Also tried on Android 2.x, same result. One thing to notice is that the buttons work perfectly on iOS devices.
The text was updated successfully, but these errors were encountered:
When you say unresponsive, do you mean that they're just hard to click? As in, the hit-area isn't large enough? If so, it might be a good idea to just increase the size of the Views that wrap the ImageViews for all of the buttons in the navigation bar.
@mcongrove forgot to give feedback. It still not worked some times. A quick fix was to create 2 transparent views floating on top/left and top/right, outside the #Wrapper element and slightly wider.
I will make some more tests and if this solves the issue I will provide a PR.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have tested this many times on many devices (Nexus 7, Nexus 5, Samsung Galaxy S4/S3, etc..) and I notice that top buttons (menu, back, etc) on Android are quite unresponsive.
I have tried several ways to resolve the issue, like assigning
touchEnabled=false
to the children images, but nothing worked so far.I'm using the
master
branch for testing purposes, using the devices mentioned above, most of them running Android 4.x. Also tried on Android 2.x, same result. One thing to notice is that the buttons work perfectly on iOS devices.The text was updated successfully, but these errors were encountered: