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
Version Number: 9.0.17-1 Reproducible in staging?: Y Reproducible in production?: N Email or phone of affected tester (no customers):applausetester+kh050806@applause.expensifail.com Issue reported by: Applause Internal Team
Action Performed:
Go to staging.new.expensify.com
Create a new workspace.
Go back to Inbox.
Open workspace switcher and select the new workspace.
Go to Search.
Navigate through the empty Search sections to check how the skeleton during loading and the skeleton in empty state are aligned differently on staging and production.
Expected Result:
The skeleton during loading and the skeleton in empty state should have similar alignment (only slight deviation on production).
Actual Result:
The skeleton during loading and the skeleton in empty state has larger deviation in alignment compared to production.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.17-1
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+kh050806@applause.expensifail.com
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
The skeleton during loading and the skeleton in empty state should have similar alignment (only slight deviation on production).
Actual Result:
The skeleton during loading and the skeleton in empty state has larger deviation in alignment compared to production.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6564170_1723020514064.20240807_164018.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @jayeshmangwani