Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After tapping someone's name to private-message them, it's hard to tap the new "tab" at the bottom, to enter the PM screen #93

Open
dholbert opened this issue May 29, 2015 · 3 comments

Comments

@dholbert
Copy link
Contributor

My STR:

  1. Open Firesea IRC app on Sony Xperia Z3 phone, in Firefox OS (3.0)
  2. Connect, w/ default values
  3. When someone says something, tap their username.
    (Note that a private message tab appears for them at bottom of screen)
  4. Try to tap the private message tab.

EXPECTED RESULTS: Switch to private message tab.
ACTUAL RESULTS: Nothing happens, or the keyboard comes up. After repeated mashing of the screen area around the tab, I can eventually get it to trigger, but it takes a while. Something is really whack about the touch events for that tab.

@dholbert
Copy link
Contributor Author

I get similar results when I try to tap the "Setup" tab, when I'm in an IRC channel tab.

@nickdesaulniers
Copy link
Owner

Indeed, we've seen Flames with really poor ability to detect touches near the edge of the screen. I wonder if expanding the height of the tabs help. @dholbert , can you remote debug via webIDE, use the inspector to add to the height of tabs, and see if that helps?

@dholbert
Copy link
Contributor Author

Indeed, we've seen Flames with really poor ability to detect touches near the edge of the screen.

Yup, I had one of those. :) I don't think that's the problem here, though, because:

  • I'm encountering this on a Xperia Z3, not a flame.
  • the touch isn't discarded (as it was on my flame w/ that dead-spot problem) - it's just mis-targeted. When I'm on the chat screen, it frequently targets the text field & brings up the keyboard (but I'm sure I tapped the tab, not the text field).
  • once I've successfully switched tabs once, it works great. It's only busted the first time (or maybe the first time after a new tab has been opened)

@dholbert , can you remote debug via webIDE, use the inspector to
add to the height of tabs, and see if that helps?

That does indeed help. (I gave <x-tabbar> a height of 120px.) I can still reproduce the problem when tapping near the top of the tabs, though (before I've successfully switched).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants