nextcloud / nextcloud/calendar

Events with long descriptions jump off past the left of the screen and can't be seen properly in day and list view

Open
#4,893 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. to triage bug design Feature: Editor
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Steps to reproduce
  1. Create or edit an event
  2. Add a long description (16+ lines in day view, 23+ lines in list view)
  3. Event jumps off to the left of the screen so half of it can be seen to be edited nor viewed, like this
Expected behavior

I expect the same behaviour as exists in week and month view. However long event descriptions are there, the events don't become un-viewable by largely jumping off the screen

Actual behaviour

Events with long descriptions jump off to the left of the screen so half of it can be seen to be edited nor viewed in both day and list view.
Screenshot from 2023-01-12 22-43-02

Calendar app version

4.2.1

CalDAV-clients used

n/a

Browser

Firefox 108.02 (64-bit), Chrome 108.0.5359.124 (Official Build) (64-bit)

Client operating system

Ubuntu 22.04.1

Server operating system

Ubuntu 20.04

Web server

None

Database engine version

None

PHP engine version

None

Nextcloud version

25.0.2

Updated from an older installed version or fresh install

Updated from an older version

List of activated apps
don't have access to that right now but can update in due course if need be
Nextcloud configuration
don't have access to that right now but can update in due course if need be
Web server error log

No response

Log file

No response

Browser log

No response

Additional info

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

No files, tests, or entry points are identified in the issue. Reproduce the problem with long descriptions in day and list views, compare their positioning with week and month views, and confirm that the event remains fully visible and editable after the fix.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.