nextcloud / nextcloud/deck

Deck comments not saved if last thing is a line break

Open
#5,337 5 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: comments
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

Since about 2-3 weeks (version 1.11.? to 1.11.2) whenever I write comments in the web GUI and I finish my last input with a line feed, the data will not be stored!

To Reproduce
Steps to reproduce the behavior:

  1. Go to deck, create a new card. See that after "Beschreibung" it will say "not saved".
    image
    After waiting a few seconds the card update will be saved, both shown by the "not saved" disappearing and the "Last changed" will say something like a few moments ago.

  2. Write some more and finish with a line break. Now you can wait forever and nothing will happen!
    image

  3. Open another card and go back to you initial card and you will see that everything you entered (when you used the line break at the end) is gone.
    image

Expected behavior
Everything should be saved, no matter if I use a line break at the end of whatever I enter.

Maybe this has something to do with this issue:
https://github.com/nextcloud/deck/issues/5326

Client details:

  • OS: Windows
  • Browser: chrome and firefox
  • Version: nextcloud 27.1.4 with deck 1.11.2

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

Reproduce the issue in the Deck web GUI by creating a card and editing its comments or description with and without a trailing line break. Compare the save behavior and persistence after navigating away and back. Done means entries ending in a line break are saved and restored normally.

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.