Openbravo Issue Tracking System - POS2 | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0050476 | POS2 | POS | public | 2022-10-11 11:27 | 2022-10-11 16:38 |
Reporter | plujan | ||||
Assigned To | Retail | ||||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Platform | OS | 5 | OS Version | ||
Product Version | |||||
Target Version | Fixed in Version | ||||
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 | 0050476: [22Q4] Infinite pop-up loop when navigating to the wrong terminal | ||||
Description | If the access URL contains a non-existent terminal, the expected pop-up is shown. However, after accepting the message, this is shown again and again. In POS1 the message is not shown again after accepting it the first time. | ||||
Steps To Reproduce | 1. Navigate to https://livebuilds.openbravo.com/retail_pi_pgsql/web/org.openbravo.retail.posterminal/?terminal=NONEXISTENT [^] 2. Notice the expected message. Accept it. The pop up is closed. 3. Navigate to https://livebuilds.openbravo.com/retail_pos2_pgsql/web/pos/?terminal=NONEXISTENT [^] 4. Notice the expected message. Accept it. Notice the pop up is shown again after accepting the previous pop up. | ||||
Proposed Solution | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2022-10-11 11:27 | plujan | New Issue | |||
2022-10-11 11:27 | plujan | Assigned To | => Retail | ||
2022-10-11 11:27 | plujan | Triggers an Emergency Pack | => No | ||
2022-10-11 16:38 | plujan | Summary | [22Q4] Inifite pop-up loop when navigating to the wrong terminal => [22Q4] Infinite pop-up loop when navigating to the wrong terminal |
There are no notes attached to this issue. |