Join the best erotica focused adult social network now
Login
Enter key issue with Android phone
Chat Moderator
I have an android also, and so far, have not had this issue.
Code Monkey
Quote by DreamKnight
Anyone else having this issue - in my Android device the return key is working like a carriage return and not like send / submit. Just started happening. Not sure if it is Lush or my phone but it makes it impossible to send a response to a black box message.
Can you clear your browser cache and try again for me. When you hit the enter key does the box grey out at all, or does this line feed behavior happen from the beginning?
Quote by gav
Can you clear your browser cache and try again for me. When you hit the enter key does the box grey out at all, or does this line feed behavior happen from the beginning?
I cleared cache and restarted my phone. No change. It does the line feed immediately. Has worked fine until today. Really strange.
Code Monkey
Quote by DreamKnight
I switched from chrome to Firefox and Firefox seems to work like Chrome used to.
Maybe there's been an update to chrome that's broken something. Chrome on windows seems to work fine. Is there such a thing as a javascript console on your android version?
Scarlet Seductress
I'm posting this using Chrome (47) on android 5.0.
Return seems to be working fine for me.
I'm using the standard keyboard as opposed to a third party app like SwiftKey.
Return seems to be working fine for me.
I'm using the standard keyboard as opposed to a third party app like SwiftKey.
Quote by Liz
I'm posting this using Chrome (47) on android 5.0.
Return seems to be working fine for me.
I'm using the standard keyboard as opposed to a third party app like SwiftKey.
I'm on Chrome (48) on Android 5.1 with the "factory" Google keyboard. I've searched for similar issues posted on the web and haven't found any. It's really strange. At least Firefox works.
"insensitive prick!" – Danielle Algo
I guess Chrome dropped support for `KeyboardEvent.keyCode`.
From Lush's code (`e.keyCode==13` references the Enter key here):
[code]$('#smsmessage').bind('keypress', function(e) {
if(e.keyCode==13){
$('#sendsms').click();
e.preventDefault();
}
});[/code]
On the Mozilla Developer Network page about KeyboardEvent.keyCode it says:
So other browsers may perhaps follow soon.
Normally, when typing in a textareas, an enter does not trigger a form submit, so I can imagine that some people will be (unpleasantly) surprised to see their message being sent when they were not ready to send it. It would be nice if this was a feature that requires opt-in.
From Lush's code (`e.keyCode==13` references the Enter key here):
[code]$('#smsmessage').bind('keypress', function(e) {
if(e.keyCode==13){
$('#sendsms').click();
e.preventDefault();
}
});[/code]
On the Mozilla Developer Network page about KeyboardEvent.keyCode it says:
Deprecated
This feature has been removed from the Web standards. Though some browsers may still support it, it is in the process of being dropped. Do not use it in old or new projects. Pages or Web apps using it may break at any time.
So other browsers may perhaps follow soon.
Normally, when typing in a textareas, an enter does not trigger a form submit, so I can imagine that some people will be (unpleasantly) surprised to see their message being sent when they were not ready to send it. It would be nice if this was a feature that requires opt-in.
=== Not ALL LIVES MATTER until BLACK LIVES MATTER ===
Scarlet Seductress
Quote by BiMale73
Technical stuff...
And that's how you get yourself a 'Bug Slayer' badge, lol.
Charming as fuck
or you could do what i did and save gav's sexy legs from the mozzies 
Quote by BiMale73
I guess Chrome dropped support for `KeyboardEvent.keyCode`.
From Lush's code (`e.keyCode==13` references the Enter key here):
[code]$('#smsmessage').bind('keypress', function(e) {
if(e.keyCode==13){
$('#sendsms').click();
e.preventDefault();
}
});[/code]
On the Mozilla Developer Network page about KeyboardEvent.keyCode it says:
So other browsers may perhaps follow soon.
Normally, when typing in a textareas, an enter does not trigger a form submit, so I can imagine that some people will be (unpleasantly) surprised to see their message being sent when they were not ready to send it. It would be nice if this was a feature that requires opt-in.
Thank you. Damn, you're good.
Ughh. That also sucks though!
"insensitive prick!" – Danielle Algo
Quote by Liz
And that's how you get yourself a 'Bug Slayer' badge, lol.
Realy?
\o/
=== Not ALL LIVES MATTER until BLACK LIVES MATTER ===
"insensitive prick!" – Danielle Algo
Quote by Barbielicious
Thank you. Damn, you're good.
Thanks, but I'm sure we all have specific knowledge related to our professions. This one just happens to be mine.
=== Not ALL LIVES MATTER until BLACK LIVES MATTER ===
"insensitive prick!" – Danielle Algo
Quote by Barbielicious
You're welcome. It's kind of hot! Lmaooo.
Tell that to Gav, I'm just yelling from the side-line ;)
=== Not ALL LIVES MATTER until BLACK LIVES MATTER ===
Active Ink Slinger
I had this when using the google standard keyboard. When I changed to swiftkey, it was fine. Seems that might be the issue.
"insensitive prick!" – Danielle Algo
Quote by Crapbag123
I had this when using the google standard keyboard. When I changed to swiftkey, it was fine. Seems that might be the issue.
That suggests the issue occurs outside of the browser, while the 'it happens in Chrome but not in Firefox' suggests it is in fact a browser issue. Weird
=== Not ALL LIVES MATTER until BLACK LIVES MATTER ===
Code Monkey
Quote by BiMale73
That suggests the issue occurs outside of the browser, while the 'it happens in Chrome but not in Firefox' suggests it is in fact a browser issue. Weird
Thanks for the investigation. No de-obfuscation of my code! *slaps*
I've put in some more robust code around the keycode checks.
Android fragmentation is a bitch.