Create Project button is too picky about what kinds of taps it likes
#128 opened on Jul 14, 2015
Repository metrics
- Stars
- (63 stars)
- PR merge metrics
- (PR metrics pending)
Description
This issue has been migrated from mozilla/webmaker-android#1932.
It was originally written by flukeout on Wed May 20 2015 and had the following description:
It's very easy to tap the Create Project button on the Make view with no effect. It seems like it only likes very quick taps, holding down your finger for even a short period of time before releasing makes the button unresponsive.
Let's not set a limit (or at least not as aggressive) to how fast the tap needs to be, especially because the "pressed state" on the button suggests that you're using it correctly even if holding it for a long time.
For reference, the Make and Discover tabs can be tapped and held for a long time before releasing your finger, and they still work.
On Wed May 20 2015, k88hudson commented:
Honestly, there is nothing on this button that could possibly make it respond differently from the others....
...however, I think this issue is appearing tto happing because we don't have a blocking loading state on creating a new project, which is also causing https://github.com/mozilla/webmaker-android/issues/1930
On Wed May 20 2015, flukeout commented:
**@**k88hudson There is definitely a difference between how some of the UI / buttons in the app work. For example, try long-pressing the 'back arrow' in the header in the Project Editor - when you finally release your finger the action works. Long-pressing the "Create Project" button doesn't work. You can't reproduce this?
On Wed May 20 2015, k88hudson commented:
Wow, you're right. Looks like the default behaviour of buttons/anything clickable in Chrome is not to trigger a "click"/"tap" if you hold down your finger for a long time. I'm guessing this is because it would be impossible otherwise to detect a "taphold" gesture.
The back buttons at the top are Android, which do not appear to have this behaviour.
It will be a very significant amount of work to override the default behaviour of onClick for all buttons/interactive elements, are you sure this is critical to the user experience?