Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0044576Retail ModulesWeb POSpublic2020-07-08 10:102021-01-25 11:48
Reporteraaroncalero 
Assigned TojavierRodriguez 
PriorityhighSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed 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 PackNo
Summary0044576: WebPOS switches from portrait mode to landscape when the mobile keyboard is shown
DescriptionThe view mode used in WebPOS is defined by the aspect ratio of the screen (the width:height relationship).
If the aspect ratio is higher than 9/8, then the WebPOS is considered to be in landscape/desktop mode and the view switches to a two-column layout.
If the aspect ratio is lower, then the WebPOS switches to a single-column layout.

In some devices, when the mobile keyboard is opened, the remaining screen space crosses the portrait/landscape aspect ratio threshold, and the screen switches to two-column mode, breaking the layout of the application
Steps To ReproduceIn a relatively small** mobile, go to livebuilds WebPOS, and click on the login inputs. The keyboard will open and the WebPOS will switch to two-column layout.

Once logged in, go to the product search, or try to create a new customer (any interaction that requires user input via keyboard); same problem will happen and the WebPOS will switch to two-column layout until the keyboard is closed.

** The issue has been reported in a Samsung Galaxy J3 (screen size 720 x 1280px) but also in a Huawei P Smart + (screen size 1080 x 2340px). Attached screenshots of both.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Filespng login-page.png (160,078) 2020-07-08 10:11
https://issues.openbravo.com/file_download.php?file_id=14739&type=bug
png

png new-edit-customer.png (150,246) 2020-07-08 10:11
https://issues.openbravo.com/file_download.php?file_id=14740&type=bug
png

png product-search.png (148,248) 2020-07-08 10:11
https://issues.openbravo.com/file_download.php?file_id=14741&type=bug
png

jpg Screenshot_20200706_164655.jpg (446,318) 2020-07-08 10:11
https://issues.openbravo.com/file_download.php?file_id=14742&type=bug
diff mobilecore.diff (1,609) 2020-11-18 09:33
https://issues.openbravo.com/file_download.php?file_id=15095&type=bug
Issue History
Date ModifiedUsernameFieldChange
2020-07-08 10:10aaroncaleroNew Issue
2020-07-08 10:10aaroncaleroAssigned To => Retail
2020-07-08 10:10aaroncaleroResolution time => 1595973600
2020-07-08 10:10aaroncaleroTriggers an Emergency Pack => No
2020-07-08 10:11aaroncaleroFile Added: login-page.png
2020-07-08 10:11aaroncaleroFile Added: new-edit-customer.png
2020-07-08 10:11aaroncaleroFile Added: product-search.png
2020-07-08 10:11aaroncaleroFile Added: Screenshot_20200706_164655.jpg
2020-08-20 15:13ranjith_qualiantech_comAssigned ToRetail => ranjith_qualiantech_com
2020-08-27 07:38ranjith_qualiantech_comAssigned Toranjith_qualiantech_com => Retail
2020-11-09 06:33marvintmResolution time1595973600 => 1605826800
2020-11-17 11:00javierRodriguezAssigned ToRetail => javierRodriguez
2020-11-18 09:33javierRodriguezFile Added: mobilecore.diff
2020-11-23 06:37marvintmNote Added: 0124556
2020-11-23 06:37marvintmTypedefect => design defect
2021-01-25 11:48marvintmResolution time1605826800 =>

Notes
(0124556)
marvintm   
2020-11-23 06:37   
We have provided a fix for this issue (you can find it as an attached patch).

However, at the same time for now we have changed it to design defect. The reason is that we are concerned with the risk of applying the patch in general. It should be safe to apply it if all devices used follow the resolution/aspect ratio of the specified device. That said, we think the risk that it may cause unexpected regressions if the devices used are slightly different is high, and currently we don't have the ability to test it properly in a sufficiently high amount of device combinations.