nextcloud / nextcloud/deck

The Ordered Number Gone When I Update A Comment in A Card

Open
#7,186 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug
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.

Describe the bug
When I comment with ordered number then update it, the number is gone and the line whitespace also gone

To Reproduce
Steps to reproduce the behavior:

  1. Add comment in a card with ordered number and add some whitespaces for each item
  2. Update it and see that the ordered number and the whitespaces are gone

Expected behavior
The Ordered Number is not gone and the spaces are consistent

Screenshots
If applicable, add screenshots to help explain your problem.

Client details:

  • OS: MacOS Sequoia 15.6.1
  • Browser: Chrome
  • Version: 1.15.2
  • Device: Laptop
Server details

Operating system: Linux

Web server: Apache

Database:

PHP version: 8.3.24

Nextcloud version: 31.0.8

Where did you install Nextcloud from: Nextcloud AIO

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 or tests are named. Start by reproducing the issue in a Deck card comment using an ordered list and deliberate whitespace, then edit and save the comment to compare the rendered result before and after. Done means the ordered numbering and spacing remain consistent after updating the comment.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.