nextcloud / nextcloud/calendar

Usability of Voting page for Meeting Proposals could be improved for mobile devices

Open
#8,721 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement mobile
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Is your feature request related to a problem? Please describe.

Votes on mobile devices with narrow viewports are really hard to manage.

Image
  1. the submit button could be hidden behind the guest-box footer
  2. to see all information, the user has to scroll horizontally and vertically
  3. the previous votings are not clear marked (as previous votings), which can confuse the user when voting expecting the marks at his previous votings would change instantly with his actions on the form.
Describe the solution you'd like
  1. hide the guest-box footer on this page
  2. the current vote and the previous votings should be explicitly marked as those (by color, background, or by a label).
  3. the current vote and the previous votings could be shown in different tabs on devices with narrow viewport, so that users can switch between them.
Describe alternatives you've considered

All considered alternatives did not lead to productive ideas.

Additional context

No response

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 Meeting Proposals Voting page on a narrow mobile viewport and locating its page and responsive layout entry points. Check the guest-box footer, scrolling behavior, and presentation of current versus previous votings; done means the submit action remains accessible, information is usable without problematic scrolling, and the voting states are clearly distinguished.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.