nextcloud / nextcloud/cookbook

Recipe edits lost when creating new steps and pasting from clipboard

Open
#2,590 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Frontend
Dominant language
HTML
Stars
641
Forks
113
Avg merge
21h 31m
Merged PRs (30d)
26

Description

Description
Changes not saved when inserting a cooking step by pasting from clipboard.

Reproduction
Steps to reproduce the behavior:

  1. Copy some text to your clipboard with a cooking instruction.
  2. Go to a recipe
  3. Click on "Edit"
  4. Scroll down to 'Instructions'
  5. Click on + Icon to "Insert entry above"
  6. Paste text from clipboard into the new empty instruction field
  7. Click "Save"

Expected behavior
Recipe reflects the changes that I just "saved"

Actual behavior
Changes are lost.

Oddly, it will save the changes if I manually edit them with the keyboard! But a lot of times, I think there are too many steps to take in one "instruction" so I will cut to clipboard from step No. 2 (for example), insert a new step below it, and paste the cut text. When I click save, step No. 2 indeed saves the changes (and loses the data formerly in it), but the new step No. 3 was never created.

If I paste the text, then type some characters in with the keyboard, then delete the extra characters, it saves properly also. That is my current workaround.

Browser
Brave Version 1.73.89 Chromium: 131.0.6778.69 (Official Build) (64-bit)

Versions
Nextcloud server version: Nextcloud Hub 8 (29.0.8)
Cookbook version: 0.11.2
Database system: PostgreSQL 16.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit (I found this at the https://cloud.mydomain.com/settings/admin/serverinfo) page

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 browser using the listed steps: add an instruction, paste clipboard text, and save the recipe. Start by tracing the recipe editor's instruction-entry handling, then confirm that a newly pasted step is persisted after saving without requiring extra keyboard input.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.