Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0031201Retail ModulesWeb POSpublic2015-10-21 13:152017-01-13 13:57
Reporterlorenzofidalgo 
Assigned Todbaz 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Versionpi 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Todbaz
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0031201: [UX] Highly visible div is incorrectly placed
DescriptionOne of the most visible divs in POS is not correctly placed. It should be fitted to the surrounding divs.
The distance between "SCAN", "BROWSE", "SEARCH" & "EDIT" divs and the div placed just under them is too small.
Steps To ReproduceLogin POS. The aforementioned divs are those ones at the top right. Watch attached image.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0029524 closed Osmany [UX] POS div is not correctly placed 
Attached Filespng BrokenLayout.png (53,610) 2015-10-21 13:15
https://issues.openbravo.com/file_download.php?file_id=8608&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2015-10-21 13:15lorenzofidalgoNew Issue
2015-10-21 13:15lorenzofidalgoAssigned To => Retail
2015-10-21 13:15lorenzofidalgoFile Added: BrokenLayout.png
2015-10-21 13:15lorenzofidalgoTriggers an Emergency Pack => No
2015-10-21 13:16lorenzofidalgoRelationship addedrelated to 0029524
2015-10-21 13:17lorenzofidalgoSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=9771#r9771
2017-01-05 11:49dbazNote Added: 0093219
2017-01-05 11:49dbazAssigned ToRetail => lorenzofidalgo
2017-01-05 11:49dbazStatusnew => acknowledged
2017-01-13 13:53lorenzofidalgoNote Added: 0093534
2017-01-13 13:53lorenzofidalgoAssigned Tolorenzofidalgo => dbaz
2017-01-13 13:56dbazStatusacknowledged => scheduled
2017-01-13 13:56dbazNote Added: 0093535
2017-01-13 13:56dbazStatusscheduled => resolved
2017-01-13 13:56dbazResolutionopen => fixed
2017-01-13 13:57dbazReview Assigned To => dbaz
2017-01-13 13:57dbazStatusresolved => closed

Notes
(0093219)
dbaz   
2017-01-05 11:49   
Could you check if it is still reproducible? (I am not able to reproduce it anymore)
(0093534)
lorenzofidalgo   
2017-01-13 13:53   
It is fixed in the last versions I have checked (RR17Q1 and pi).
(0093535)
dbaz   
2017-01-13 13:56   
It is already fixed. No change required.