You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The layout of the order summary table on pages cart and order summary is too wide to fit the screen of mobile devices. Especially the very long names of applied enterprise fees could be a problem here.
Expected Behavior
The layout should fit the screen without scrolling horizontally.
Actual Behaviour
The layout doesn't fit the screen and the user needs to scroll horizontally or zoom out.
Steps to Reproduce
Use a mobile device or Browserstack
Make sure split checkout is activated
Proceed to checkout or to cart
Observe the cart and order summary table
Animated Gif/Screenshot
Chrome on Galaxy S22
Workaround
Zoom or scroll horizontally.
Severity
bug-s3: a feature is broken but there is a workaround
Browser name and version: Firefox mobile, Safari mobile, Chrome mobile
Operating System and version (desktop or mobile): Android, iOS
Possible Fix
The text was updated successfully, but these errors were encountered:
drummer83
added
the
bug-s3
The bug is stopping a critical or non-critical feature but there is a usable workaround.
label
Nov 10, 2022
sigmundpetersen
changed the title
[Split checkout] Cart and order summary don't fit to screen on mobile devices
[Split Checkout] Cart and order summary don't fit to screen on mobile devices
Nov 11, 2022
Description
The layout of the order summary table on pages cart and order summary is too wide to fit the screen of mobile devices. Especially the very long names of applied enterprise fees could be a problem here.
Expected Behavior
The layout should fit the screen without scrolling horizontally.
Actual Behaviour
The layout doesn't fit the screen and the user needs to scroll horizontally or zoom out.
Steps to Reproduce
Animated Gif/Screenshot
Chrome on Galaxy S22
Workaround
Zoom or scroll horizontally.
Severity
bug-s3: a feature is broken but there is a workaround
Your Environment
Possible Fix
The text was updated successfully, but these errors were encountered: