Openbravo Issue Tracking System - POS2 |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0047058 | POS2 | Restaurants | public | 2021-06-10 17:25 | 2021-08-18 11:55 |
|
Reporter | timothee_catteeuw | |
Assigned To | hernan-dp | |
Priority | normal | Severity | major | Reproducibility | sometimes |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | TAP | Fixed in Version | TAP | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0047058: JIRA 1836 - Arrows to review on Keymap |
Description | We encounter difficulties with arrows on keymap, in fact for an optimal utilization, we think :
- display every time the arrow without hiding it
- resize the arrow because sometimes, it is very difficult to press it
- and/or put it on another place, because sometimes we touch the bouton instead of the arrow, and it is mandatory to touch again the screen
All these scénérii has to be developped by testing on flunch till (F11/fulll screen mode) |
Steps To Reproduce | Cf. video in related Jira |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | depends on | defect | 0047540 | | closed | hernan-dp | JIRA 1836 - Arrows to review on Keymap |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2021-06-10 17:25 | timothee_catteeuw | New Issue | |
2021-06-10 17:25 | timothee_catteeuw | Assigned To | => Retail |
2021-06-10 17:25 | timothee_catteeuw | Triggers an Emergency Pack | => No |
2021-06-14 10:28 | guilleaer | Target Version | TAP => |
2021-06-14 12:15 | dmiguelez | Status | new => feedback |
2021-06-18 11:53 | timothee_catteeuw | Note Added: 0129651 | |
2021-07-16 11:32 | dmiguelez | Note Added: 0130535 | |
2021-07-16 11:32 | dmiguelez | Status | feedback => closed |
2021-07-16 11:32 | dmiguelez | Resolution | open => invalid |
2021-08-11 14:24 | dbaz | Note Added: 0131077 | |
2021-08-12 13:28 | jmelin | Status | closed => new |
2021-08-12 13:28 | jmelin | Resolution | invalid => open |
2021-08-12 13:54 | guilleaer | Resolution time | => 1630015200 |
2021-08-12 13:54 | guilleaer | Assigned To | Retail => hernan-dp |
2021-08-12 13:54 | guilleaer | Status | new => acknowledged |
2021-08-12 13:54 | guilleaer | Status | acknowledged => scheduled |
2021-08-18 11:45 | guilleaer | Type | defect => backport |
2021-08-18 11:46 | guilleaer | Note Added: 0131173 | |
2021-08-18 11:50 | guilleaer | Target Version | => TAP |
2021-08-18 11:55 | dmiguelez | Note Added: 0131177 | |
2021-08-18 11:55 | dmiguelez | Status | scheduled => resolved |
2021-08-18 11:55 | dmiguelez | Fixed in Version | => TAP |
2021-08-18 11:55 | dmiguelez | Resolution | open => fixed |
2021-08-18 11:55 | dmiguelez | Status | resolved => closed |
Notes |
|
|
Thanks to David analyze explanation done to the client , mainly he is waiting for the last corrections on carrousel, we agreed to test these corrections before. |
|
|
|
Changes in carrousel fixes the problem |
|
|
(0131077)
|
dbaz
|
2021-08-11 14:24
|
|
After analyzing, we will keep the arrow the same size, because it is intended to be pressed using the mouse. We will only display it on hover effects, although the target area to do the hover effect will change (explained later) and we will move to the border of the button area to avoid mis-taps using touchscreens.
So, in order to move the buttons to the borders, we will need
.obc2CarrouselButtonStyle-Right {
right: -0.85rem;
...
}
.obc2CarrouselButtonStyle-Left {
left: -1rem;
...
}
and in order to increase the area in which the hover effect (highlight or yellow background of the arrow button) will take place, we need, programmatically in javascript, to capture the on mouse over event of the first/last column/row buttons, to ensure that once this happens, the hover style (yellow background) of the next/previous page arrow buttons happens.
Here there is a video explaining both things in detail: https://youtu.be/rkWwrnKhtUQ [^] |
|
|
|
|
|
|
|