nextcloud / nextcloud/calendar
Better alignment in small event card
Open
Nobody has claimed this yet.
1. to develop
bug
design
Feature: Editor
papercut
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Steps to reproduce
- Open calendar
- Create an event with details and save
- click on the event you just created to open the event card
Expected behavior
- Icons are all center aligned (changed to
.property-text__icon { padding-left: 6px; }andpadding-left: 8px;for just the attendees icon - Text is all left aligned (changed to
.property-title-time-picker__time-pickers { margin-inline-start: 0px;}) - There is more padding around the content (changed to
.event-popover { padding: calc(var(--default-grid-baseline)*4); padding-top: calc(var(--default-grid-baseline)*2); })
Actual behavior
elements are too close to the edges and not aligned
Calendar app version
No response
CalDAV-clients used
No response
Browser
No response
Client operating system
No response
Server operating system
No response
Web server
None
Database engine version
None
PHP engine version
None
Nextcloud version
No response
Updated from an older installed version or fresh install
None
List of activated apps
Nextcloud configuration
Web server error log
Log file
Browser log
Additional info
No response
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
Reproduce the issue by opening the calendar, creating an event, and opening its event card, then search the event-card styles for .property-text__icon, .property-title-time-picker__time-pickers, and .event-popover. Done means the icons and text are aligned as described and the card has the requested padding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100