Firefox has been giving me a serious number of issues lately *shakes fist at sky* - if it turns out that it we can get a reproducible set of steps, it's definitely something that I'd like to look into.
So, this is a little bit of madness. I've dug deep into it, and for that input field ONLY, firefox mobile fires off the TAB key when you press the enter/return key. In contrast, searching in the vocab dictionary will have firefox register the ENTER key, as expected. To be honest, this sounds like a firefox bug, although just about the weirdest one I've ever heard. I am not sure what, if any, javascript knowledge you have, but to the best of my understanding, checking to see which keycode was pressed should not be affected in any way by anything the html or the rest of the javascript should be able to affect.
Wow... That is not expected at all... I did some tests on a test page and could not reproduce that issue. Maybe it has something to do with a wrapper form?
Basically, firefox is making a mistake. It THINKS there are other form fields available, so the "enter" button is actually trying to move to the next form field.
There ARE other form fields there (like the sorting dropdown), but chrome will correctly ignore it because it's not visible. Firefox seems to not pick up on that, and that is why my "enter/return button" catcher is not working - Firefox is actually sending a tab because that is the keyboard button you usually push to advance to the next field on a form.
