Download & Extend

Keyboard on ipad, android popping up when using POS, making virtually unusable

Project:UberPOS
Version:6.x-1.x-dev
Component:User interface
Category:bug report
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

I can get uberpos to work if I use my mouse to click the enter button, but if I press enter on the keyboard my entire order disappears. It also happens when scanning bar codes and swiping credit cards.

Any help would be appreciated!

Thanks.

Comments

#1

Hey,
Can you give some more info on the problem? When did this problem start, and what browser(s) does it happen in? Does it happen regardless of what command you are entering?

#2

I've narrowed it down to happening on internet explorer. Firefox doesn't display this issue.

It happens with they keyboard, bar code scanner, and card reader.

Thanks.

#3

Status:active» needs review

Thanks, got it. Let me know how this patch works.

AttachmentSize
uberpos-859904.patch 1003 bytes

#4

Status:needs review» patch (to be ported)

This should be fixed in the latest 6.x development version.

#5

Title:Keyboard enter command resets uberpos and erases the entire order.» Keyboard on ipad, android popping up when using POS, making virtually unusable
Category:support request» bug report
Status:patch (to be ported)» active

Hi,

Love the idea of this module, and giving feedback to make better hopefully, have an issue with tablet/ipad access.

When you are using the POS on a browser on a tablet, after each ajax push on the keyboard, causes the keyboard to popup. Ive been googling around, and there seems to be a setting which might help.

Seems the issue is related to the focus being sent to the text box, causing the keyboard to popup, but this makes the client terrible to use on these devices.

As I understand it, its the focus to the testbox where the values are placed. Can this be refocused back to the ajax button?

this is a suggestion, but Im still trying to see if it can be added in. Any thoughts about this issue, gratefully received.

this.getWindow().setSoftInputMode(WindowManager.LayoutParams.SOFT_INPUT_STATE_ALWAYS_HIDDEN);

imagine this would occur for 6 and 7

regards