nextcloud / nextcloud/calendar
13" Macbook NextCloud Calendar issue
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
Dear NextCloud team,
I tried to create a meeting invite on 13" MacBook and the screen appears to be too small to see the SAVE button:
(yes, of course, I tried to scroll and used the Tab button, etc.).
When I projected this same (!) window on a larger monitor, then the SAVE button was visible:
Thanks
anton
Expected behaviour
Tell us what should happen
Actual behaviour
Tell us what happens instead
Server configuration
Operating system: Ubuntu/RedHat/...
Web server: Apache/Nginx
Database: MySQL/Maria/SQLite/PostgreSQL
PHP version: 8.1/8.2/8.3
Nextcloud Version: (see administration page)
List of activated apps:
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your server installation folder
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing meeting-invite creation on the 13-inch MacBook-sized display described in the issue and compare it with the larger-monitor view. Inspect the calendar interface responsible for the invite form and determine why the SAVE button is not visible or reachable; done means the button is usable at the smaller size. The issue does not name a file, test, or complete server configuration.
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
- Needs clarification
- Newbie friendliness
- 35/100