nextcloud / nextcloud/deck

formatting bar should always be visible (floating)

Open
#6,091 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug regression
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

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.

To Reproduce
Steps to reproduce the behavior:

  1. add a really long description to a Deck card, so that the top of the card (title, due date, edit bar...) can not be seen anymore
  2. now you want to turn something into a numbered list for example
  3. you have to scroll all the way to the top of the card to click on the icon in the edit bar, then scroll down again

Expected behavior
as in the normal .md editor, the edit bar should float at the top of the viewport, no matter where in the text I am, so I can quickly access it

Screenshots
editing bar is there:
image
editing bar gone:
image

Details
NC 29.0.3 on cloud.nextcloud.com - not sure which Deck version

Alternatives
yeah, there are some ways to get formatting with shortcuts, or by adding "-" for a list, but that is not enough

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 locating the Deck card editor and its formatting bar, then reproduce the issue with a long card description. Done means the formatting bar remains accessible at the top of the viewport while scrolling through the description, including when applying a numbered list.

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.