Openbravo Issue Tracking System - POS2 | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0053537 | POS2 | Core | public | 2023-09-25 13:56 | 2023-09-25 13:56 |
Reporter | cberner | ||||
Assigned To | Triage Platform Base | ||||
Priority | normal | Severity | major | 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 | 0053537: ConfigurableLayout items can collide in the same position and are not detected | ||||
Description | Currently, ConfigurableLayout elements may be in the same position as another element of the same ConfigurableLayout configuration, resulting in one overlapping the other. We should detect collisions of ConfigurableLayout elements when the component is being rendered and generate a warning to inform the developer about this problem. Terminal log should be generated. It would be nice to detect this cases in cypress tests(warnings generated making tests fail). | ||||
Steps To Reproduce | Create a ConfigurableLayout .config.json file and use it in a component. That .config.json should have 2 elements with the same row + column positions. The change is not detected when rendered, and the last element is the one that prevails in front of the previous one. | ||||
Proposed Solution | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2023-09-25 13:56 | cberner | New Issue | |||
2023-09-25 13:56 | cberner | Assigned To | => Triage Platform Base | ||
2023-09-25 13:56 | cberner | Triggers an Emergency Pack | => No |
There are no notes attached to this issue. |