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
There are two major inconsistencies in how custom status updates work in the web client:
🐛 Issues Identified:
Empty Custom Status ("") Behavior:
When a user sets their custom status as an empty string (""), a toast message appears confirming that the status has been updated.
However, in reality, the status does not get updated, meaning the server rejects the empty value (""), but the UI does not reflect this rejection.
Inconsistent Status Button Behavior:
When selecting status options like "Online," "Busy," "Away," or "Offline", only the status icon updates, but the textual custom status remains unchanged.
However, selecting "Meeting" does update the textual custom status to "Meeting".
This inconsistency makes the user experience confusing and should be fixed for consistency.
Steps to reproduce:
Click on your profile icon.
Click on meeting status, changing the status to meeting and then do the below, if not set at meeting, the function works fine.
Checkout various status options, they only change the status icon but not the text.
The meeting button does change the text to meeting.
Go to custom status, and make the input field blank (i.e. delete fetched status text).
Submit, you will receive success toast.
Again open the custom status modal, you will see that youre status is the same that you wanted to delete.
Expected behavior:
For Empty Custom Status ("") Issue:
Either prevent the user from submitting an empty status OR
Show a toast message stating: "Custom status cannot be empty."
Alternatively, if keeping an empty status is valid, the server should allow it.
For Status Button Consistency:
All status buttons (Online, Busy, Away, Offline, Meeting) should update both the status icon and the textual custom status, ensuring consistent behavior.
Actual behavior:
20250301-1049-17.7560462.mp4
Server Setup Information:
Testing on Prod
Client Setup Information
Desktop App or Browser Version:Browser
Operating System: WSL
Additional context
Relevant logs:
The text was updated successfully, but these errors were encountered:
Description:
There are two major inconsistencies in how custom status updates work in the web client:
🐛 Issues Identified:
Empty Custom Status (
""
) Behavior:""
), a toast message appears confirming that the status has been updated.""
), but the UI does not reflect this rejection.Inconsistent Status Button Behavior:
Steps to reproduce:
Expected behavior:
For Empty Custom Status (
""
) Issue:For Status Button Consistency:
Actual behavior:
20250301-1049-17.7560462.mp4
Server Setup Information:
Client Setup Information
Additional context
Relevant logs:
The text was updated successfully, but these errors were encountered: