Openbravo Issue Tracking System - Retail Modules
View Issue Details
0022217Retail ModulesWeb POSpublic2012-11-06 15:392012-12-21 13:34
rgoris 
guilleaer 
normalminoralways
closedno change required 
5
 
 
No
0022217: List views cannot be swiped on Safari
This is tested on live builds using Safari on Windows 7 and Windows 8 using both Dell and Asus devices.

In BROWSE and SEARCH the lists cannot be swiped. Nothing moves.
Go to BROWSE tab and swipe a product list.
multibrowser
Issue History
2012-11-06 15:39rgorisNew Issue
2012-11-06 15:39rgorisAssigned To => adrianromero
2012-11-09 11:51alostaleStatusnew => scheduled
2012-11-09 11:51alostaleAssigned Toadrianromero => guilleaer
2012-11-09 11:51alostalefix_in_branch => pi
2012-11-09 11:51alostaleTag Attached: multibrowser
2012-11-14 11:09guilleaerNote Added: 0054219
2012-11-15 11:54guilleaerPriorityurgent => normal
2012-11-15 11:54guilleaerfix_in_branchpi =>
2012-11-15 11:55guilleaerNote Added: 0054263
2012-12-05 19:41adrianromeroSeveritycritical => minor
2012-12-05 19:43adrianromeroNote Added: 0054738
2012-12-12 10:00guilleaerNote Added: 0054879
2012-12-12 11:01guilleaerNote Added: 0054880
2012-12-13 09:41guilleaerNote Added: 0054905
2012-12-13 09:42guilleaerNote Added: 0054906
2012-12-13 09:42guilleaerStatusscheduled => resolved
2012-12-13 09:42guilleaerFixed in Version => RMP18
2012-12-13 09:42guilleaerResolutionopen => fixed
2012-12-21 13:32marvintmStatusresolved => new
2012-12-21 13:32marvintmResolutionfixed => open
2012-12-21 13:32marvintmFixed in VersionRMP18 =>
2012-12-21 13:34marvintmNote Added: 0055156
2012-12-21 13:34marvintmStatusnew => closed
2012-12-21 13:34marvintmResolutionopen => no change required

Notes
(0054219)
guilleaer   
2012-11-14 11:09   
Using window 7 and Safari (5.1.7) I can't reproduce this issue. All is working fine...
(0054263)
guilleaer   
2012-11-15 11:55   
Decreasing priority because this issue just affects to windows 8.
(0054738)
adrianromero   
2012-12-05 19:43   
Setting severity to minor because the environment used to reproduce the issue is not a primary target.

The primary browser for windows is Chrome.
(0054879)
guilleaer   
2012-12-12 10:00   
I've tested it using windows 8 and safari. All works fine.

Note: Depending on the browser, the swype action can be different.
If the browser detects that you are using a mobile device then swyping will be done like in a smartphone or ipad (gestures) .
If the browser detects that you are using a PC with a touch screen, swiping will be done using the scrollbar.

In case of safari in windows 8 the scrollbar should be used to swipe the lists, however using chrome you can swype by gestures.

Issue: Why enyo allows gestures to swiping for chrome and not for safari?
I'will contact with enyo.
(0054880)
guilleaer   
2012-12-12 11:01   
https://enyojs.atlassian.net/browse/ENYO-1673 [^]
(0054905)
guilleaer   
2012-12-13 09:41   
Enyo's answer:

Different scroll strategies are used on different platforms to optimize scrolling performance. On Desktop platforms, we default to using the native scrollers, which are platform/browser specific (for example, you'll notice on Windows you'll get a scroll bar, whereas on Mac Lion+, you'll only see scroll thumbs while scrolling, ala iOS-- point being, how the scroller is implemented on desktop browsers varies). My guess is that the native scroller on Chrome for Win8 accepts scroll gestures for scrolling, and Safari doesn't.
If you'd like to guarantee the same experience, you can set touch:true on a scroller/list, which forces it to use Enyo's JavaScript-based touch scroller on all platforms, which accepts both swipe and scroll-wheel scrolling (but doesn't have a dedicated scroll bar).

summary:
We cannot do anything with this problem because is safari browser who manages the gesture scrolling.
(0054906)
guilleaer   
2012-12-13 09:42   
We cannot do anything with this problem because as enyo's guys said, is safari browser who manages the gesture scrolling.
(0055156)
marvintm   
2012-12-21 13:34   
This issue cannot be fixed until Safari is changed. The problem lies in the browser, because it is not issuing the events correctly.