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
It's not reproducible consistently, but I have seen this almost always every time loading order details for the first or second time. I can reproduce this in both phone and tablet.
To Reproduce
Steps to reproduce the behavior:
Go to the orders tab
Tap on an order if split view is not enabled
Scroll down to the Customer section --> check if the "View Billing Information" row becomes center aligned horizontally shortly after order details are loaded
Screenshots
Screencast - 3 orders were loaded, for the second order the row became misaligned after the order was loaded:
trimmed.mp4
Expected behavior
The "View Billing Information" row should remain aligned on the leading edge like other rows in the view.
Isolating the problem (mark completed items with an [x]):
I have deactivated other plugins and confirmed this bug occurs when only WooCommerce plugin is active.
This bug happens with a default WordPress theme active, or Storefront.
I can reproduce this bug consistently using the steps above.
Mobile Environment
Please include:
Device: any
iOS version: iOS 18
WooCommerce iOS version: 21.8
The text was updated successfully, but these errors were encountered:
Describe the bug
It's not reproducible consistently, but I have seen this almost always every time loading order details for the first or second time. I can reproduce this in both phone and tablet.
To Reproduce
Steps to reproduce the behavior:
Screenshots
Screencast - 3 orders were loaded, for the second order the row became misaligned after the order was loaded:
trimmed.mp4
Expected behavior
The "View Billing Information" row should remain aligned on the leading edge like other rows in the view.
Isolating the problem (mark completed items with an [x]):
Mobile Environment
Please include:
The text was updated successfully, but these errors were encountered: