Using ~ in notes are prepended with \ when copied
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 738
- Forks
- 162
- Avg merge
- 6h 2m
- Merged PRs (30d)
- 35
Description
Please make a clear and concise description of what the bug is.
Notes containing a ~ and copied are pasted as \~ with a prepended \
Steps to reproduce
1.create a note with a ~
2.copy the note
3.paste in a text editor
Expected behaviour
Note text is pasted as is
Actual behaviour
all ~ are prepended with a \
Server
Please complete the following information.
- Nextcloud Server version:
Nextcloud 32.0.3
- Operating system and version:
#1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16)
- Web server and version:
Server version: Apache/2.4.65 (Debian)
- Reverse proxy and version:
nginx version: openresty/1.27.1.2
- PHP version:
PHP 8.3.29 (cli) (built: Dec 29 2025 23:29:58) (NTS)
- Is this the first time you've seen this error? (Yes / No):
yes
- When did this problem seem to first start?
prob direct after installation
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
OMV Container
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
nope
Nextcloud configuration:
Client
Please complete the following information.
- Browser (incl. version): Firefox 14
- OS: Fedora 43
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
Start by reproducing the issue in the Notes editor using a note containing ~, then copy it into a plain-text editor and compare the pasted text with the original. Trace the copy path in the JavaScript notes frontend and verify that copied note text preserves ~ without a prepended backslash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, markdown
- Domain
- content, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100