We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 3471

Summary: pressing space on Moto X generates keydown but not textinput
Product: SDL Reporter: raincomplex
Component: eventsAssignee: Sylvain <sylvain.becker>
Status: RESOLVED ABANDONED QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2    
Version: 2.0.4   
Hardware: ARM   
OS: Android (All)   

Description raincomplex 2016-10-25 21:51:03 UTC 
Android Moto X reports keydown events for the space key, but not textinput events. Possibly related to #3382, but the Moto X doesn't have a hardware keyboard.

Unfortunately I do not have a Moto X to directly test against (I got the event info from analytics), but the issue is not present on many other devices (iOS and Android). Will just work around, but figured I should report it.
Comment 1 Sylvain 2017-08-12 08:24:42 UTC 
Just wondering what is the space key if there is no hardware keyboard ?
I dont have a Moto X neither, do you still have the issue ?
Comment 2 raincomplex 2017-08-12 13:21:44 UTC 
It was the software keyboard space key. AFAIK the bug is still present but unfortunately I have no way of testing it. It only affected Moto X users (of which there were only a couple) and we worked around it, so it ended up not being a problem.
Comment 3 Sylvain 2017-08-12 19:35:45 UTC 
I have no Moto X neither, and it works fine on my devices.

As  you said, it looks like the bug #3382.
Are you sure that the code you ship has the patch from #3382 ?
Comment 4 Ryan C. Gordon 2018-08-06 21:20:24 UTC 
Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.