nextcloud / nextcloud/server

Inconsistent status change interaction

Open
#23,276 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop 25-feedback bug design feature: status
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

Steps to reproduce
  1. Open the top right menu and click the status icon
  2. Click on "Do not disturb"
  3. Click outside the dialog to close it
  4. Open the top right menu and check the current status
  5. Now click the status menu item again
  6. Pick a custom icon + enter a funny status text
  7. Click outside the dialog to close it
  8. Check status in top right menu
Expected behaviour

Status changed when clicking outside.

Actual behaviour

For the main status boxes on the top of the dialog, clicking outside is enough to save.
For the custom status line (custom or any other state), it doesn't save when clicking outside.

On my screen the "Save" button at the bottom is not directly visible on my screen so multiple times I didn't think of trying to scroll down. Also, there are other dialogs where clicking outside is enough for saving.

Client configuration
  • Firefox 80
  • Plasma/KDE
  • Font sizes set to 144 DPI instead of 96 DPI due to small screen / highdpi (full hd)
image
Server configuration

Observed on cloud.nextcloud.com

Nextcloud version: 20.0.0.9

@nickvergessen @rullzer as discussed

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the status dialog with the listed steps, comparing the main status boxes with the custom status line when the dialog is closed outside. Trace the frontend entry point for the top-right status menu and verify that the custom status is saved on outside-click; confirm the behavior with a regression test if the project provides one.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.