-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copying text from collective page copies it as markdown when text is expected #1300
Comments
Dear @pascalBokBok, which Nextcloud version to you run? With Nextcloud 28.0.5, we added some related fixes. We discussed this behaviour extensively and decided to copy markdown in most cases but skip marks (like bold, italic, ...). In cases like bulletin lists or numbered lists, markdown actually makes more sense than just the plain text. See nextcloud/text#5487 for some further context. |
Dear @mejo- But, if I may ask, since it's part fixed. Why is it that you don't just store the both text/raw and text/markdown in the copy event instead of putting a hybrid into text/raw? |
Good news then, upgrading will solve your issue 😊
The reason is that |
Describe the bug
When you copy text from e.g. an instruction page with bullets you will get the formatting as part of it
1. 1. * * cp file.txt folder-name
which makes unconvenient for storing text that can be copied.This is a new behaviour. It used to copy fine on an earlier release.
I assume it was added to easily keep formatting when copying around in collectives. I suspect that the mimetype text/markdown should also be used when copy pasting within collectives.
something akin to:
event.clipboardData.setData('text/plain', selectedText); event.clipboardData.setData('text/html', htmlContent); event.clipboardData.setData('text/markdown', markdownContent);
To Reproduce
Steps to reproduce the behavior:
Expected behavior
text without markdown formatting.
Screenshots
If applicable, add screenshots to help explain your problem.
Server details:
Client details:
The text was updated successfully, but these errors were encountered: