| 2016-03-22 20:11:41 |
Josh Stompro |
description |
EG 2.8.4
The issue we are seeing is that if a customer presses the tab key the cursor focus will move on to the next element. This causes the next scan to have no effect, if the focus is on the print list button, a receipt gets printed in response to the newline after the scan. Once the print list button is removed, then a tab takes the focus to the home button, so a scan would reload the checkout screen, but would loose the barcode just scanned.
So we have customers that either hit the enter key or via the touch screen change the focus, then scan all their items without looking at the screen, and don't notice that they haven't checked out more than the first one or two items.
It would be nice if there is nothing that the user can accidentally do on the checkout screen that would cause their next scan to fail.
A possible solution would be to tightly control the focus of the scan box on the checkout screen, and disable the scan box for the other screens where other input may be wanted/needed.
Some googling brought me to this example that disables the tab index, and moves the focus back to the text box onblur. I don't know if this is the correct way to handle it, but it might be a start.
http://jsfiddle.net/QcSPB/10/
Thanks
Josh |
EG 2.8.4
The issue we are seeing is that if a customer presses the tab key the cursor focus will move on to the next element. This causes the next scan to have no effect, if the focus is on the print list button, a receipt gets printed in response to the newline after the scan. Once the print list button is removed, then a tab takes the focus to the home button, so a scan would reload the checkout screen, but would loose the barcode just scanned.
So we have customers that either hit the tab key or via the touch screen change the focus, then scan all their items without looking at the screen, and don't notice that they haven't checked out more than the first one or two items.
It would be nice if there is nothing that the user can accidentally do on the checkout screen that would cause their next scan to fail.
A possible solution would be to tightly control the focus of the scan box on the checkout screen, and disable the scan box for the other screens where other input may be wanted/needed.
Some googling brought me to this example that disables the tab index, and moves the focus back to the text box onblur. I don't know if this is the correct way to handle it, but it might be a start.
http://jsfiddle.net/QcSPB/10/
Thanks
Josh |
|
