Set Default Avatar - Button Remains Clickable Even When Avatar Is Already Default

Description:

When the user’s avatar is already set to the default avatar, the “Set Default Avatar” button is still enabled and can be clicked repeatedly (every minute).

This leads to unnecessary API calls and confusing UX. Ideally, once the avatar is already default, the action should be disabled.

Steps to reproduce:

1. Go to Profile.
2. Select Set Default Avatar.
3. Click Set Default Avatar again (and again after any interval).

Expected behavior:

• If the current avatar is already the default, the Set Default Avatar button should be disabled.
• No API call should be triggered when the avatar is already default.
• The UI should clearly indicate that the avatar is already set to default.

Actual behavior:

• Even after setting the avatar to default, the Set Default Avatar button remains enabled.
• Users can click the button repeatedly (even every minute).
• Each click triggers the same API action despite no avatar change.
• This causes redundant requests.

Server Setup Information:

• NodeJS Version: 22.16.0
• MongoDB Version: 8.0.6

Client Setup Information

• Desktop App or Browser Version: Chrome 135.0.7049.85 (Official Build) (arm64)
• Operating System: macOS Sequoia 15.3.2

Video

https://github.com/user-attachments/assets/d6a63ab3-c0d6-4a52-8b20-fdd0d9d1567b

Start at the Profile screen and trace the Set Default Avatar button and its request path. Reproduce the repeated-click behavior, then verify that the button is disabled, the UI indicates the avatar is already default, and no API call occurs in that state.