Project:
| View Revisions: Issue #47155 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0047155: [UX] Scrolling the lines of a ticket in a Windows 7 touch screen does no behave as expected | ||
| Revision | 2021-06-16 12:39 by plujan | ||
| Steps To Reproduce | For problem 1: 1. In a ticket with more than 20 lines, swipe up or down in the ticket area to scroll the lines. 2. [Other systems] The gesture has some inertia, so when it finishes, the lines keep moving or a while. 3. [Windows 7] Notice that when the gesture finishes, the lines do not continue its movement. 4. [Windows 7] Check the gesture in the Order window and the Customer window. Notice those grids do have the intertia the ticket area has not. For problem 2: 1. In a ticket with more than 20 lines, drag the lateral scrollbar in the ticket area to scroll the lines. 2. [Other systems] The scrollbar is dragged and the user can scroll the lines. 3. [Windows 7] Notice that the scrollbar is not draggable. 4. Notice that in both cases tapping after/before the bar allows scrolling For problem 3: 1. In a ticket with more than 20 lines, swipe down until reaching the end of the ticket. Keep swiping down three more times 2. [Other systems] Swipe up once and check that, as expected, the ticket lines move 3. [Windows 7] Swipe up once and check that the lines do not move. Swipe up again, the lines do not move. Again, nothing. Finally, after the fourth swipe, the lines get moving. It looks like the number of swippings done in step 1 were "saved" and the component is expecting the same amount of swipes backwards to react. 4. Notice the same scenario applies to swiping up at the beginning of the ticket. |
||
| Revision | 2021-06-16 12:38 by plujan | ||
| Steps To Reproduce | For problem 1: 1. In a ticket with more than 20 lines, swipe up or down in the ticket area to scroll the lines. 2. [Other systems] The gesture has some intertia, so when it finishes, the lines keep moving or a while. 3. [Windows 7] Notice that when the gesture finishes, the lines do not continue its movement. 4. [Windows 7] Check the gesture in the Order window and the Customer window. Notice those grids do have the intertia the ticket area has not. For problem 2: 1. In a ticket with more than 20 lines, drag the lateral scrollbar in the ticket area to scroll the lines. 2. [Other systems] The scrollbar is dragged and the user can scroll the lines. 3. [Windows 7] Notice that the scrollbar is not draggable. 4. Notice that in both cases tapping after/before the bar allows scrolling For problem 3: 1. In a ticket with more than 20 lines, swipe down until reaching the end of the ticket. Keep swiping down three more times 2. [Other systems] Swipe up once and check that, as expected, the ticket lines move 3. [Windows 7] Swipe up once and check that the lines do not move. Swipe up again, the lines do not move. Again, nothing. Finally, after the fourth swipe, the lines get moving. It looks like the number of swippings done in step 1 were "saved" and the component is expecting the same amount of swipes backwards to react. 4. Notice the same scenario applies to swiping up at the beginning of the ticket. |
||
| Revision | 2021-06-16 11:57 by plujan | ||
| Steps To Reproduce | For problem 1: 1. In a ticket with more than 20 lines, swipe up or down in the ticket area to scroll the lines. 2. [Other systems] The gesture has some intertia, so when it finishes, the lines keep moving or a while. 3. [Windows 7] Notice that when the gesture finishes, the lines do not continue its movement. 4. [Windows 7] Check the gesture in the Order window and the Customer window. Notice those grids do have the intertia the ticket area has not. For problem 2: 1. In a ticket with more than 20 lines, drag the lateral scrollbar in the ticket area to scroll the lines. 2. [Other systems] The scrollbar is dragged and the user can scroll the lines. 3. [Windows 7] Notice that the scrollbar is not draggable. 4. Notice that in both cases tapping after/before the bar allows scrolling For problem 3: 1. In a ticket with more than 20 lines, swipe down until reaching the end of the ticket. Keep swiping down three more times 2. [Other systems] Swipe up once and check that, as expected, the ticket lines move 3. [Windows 7] Swipe up once and check that the lines do not move. Swipe up again, the lines do not move. Again, nothing. Finally, after the fourth swipe, the lines get moving. It looks like the number of swipping done in step 1 were "saved" and the component is expecting the same amount of swipe backwards to react. 4. Notice the same scenario applies to swiping up at the beginning of the ticket. |
||
| Revision | 2021-06-16 11:43 by plujan | ||
| Steps To Reproduce | 1. | ||
| Copyright © 2000 - 2009 MantisBT Group |
 |