Openbravo Issue Tracking System - Retail Modules
View Issue Details
0037413Retail ModulesWeb POSpublic2017-11-28 20:482017-11-28 20:48
dbaz 
Retail 
urgentmajoralways
newopen 
10with touch-screen
 
 
No
0037413: [UX] Default Chrome behavior while swiping left or right should be overridden
There is a feature of Chrome present in Windows with touch-enabled screens, that allows move forward and backward in the browser history by swiping left and right the screen.

This "swipe to go back in the browser history" can be executed also in the WebPOS and SCO by swipping left (or right) in any place where there be a list (receipt, browse products, ...).

This Chrome's feature can be disabled by entering the following address:
chrome://flags/#overscroll-history-navigation [^]
and setting as disabled the "Overscroll history navigation" preference (and restarting Chrome).

The point is that, as far as possible, WebPOS and SCO should work with the Chrome browser out-of-the-box without tweaking any preference. This also avoids a lot of noise regarding users experiencing annoying things while using our products.

I have prepared (and attached) a simple html example (ChromeHistorySwipe.html) that get rides of this behavior using Javascript.
Note: the 'preventDefault' of touch events cannot be done at <body> level, so the function should apply to a container (<div>) wrapping the whole page. In the WebPOS/SCO environment, the <div> with id "terminal" is a good candidate to add the event listeners and the logic.

Here there is also a video showing the problem, and the html I have prepared that fixes it: https://www.youtube.com/watch?v=9dsK1WBJFxo [^]
Read the 'Description' section.
Read the 'Description' section.
No tags attached.
html ChromeHistorySwipe.html (3,787) 2017-11-28 20:48
https://issues.openbravo.com/file_download.php?file_id=11339&type=bug
Issue History
2017-11-28 20:48dbazNew Issue
2017-11-28 20:48dbazAssigned To => Retail
2017-11-28 20:48dbazFile Added: ChromeHistorySwipe.html
2017-11-28 20:48dbazTriggers an Emergency Pack => No

There are no notes attached to this issue.