Skip to content
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

Inserted Attachments are not saved in modal view #2484

Closed
reox opened this issue Oct 29, 2020 · 2 comments
Closed

Inserted Attachments are not saved in modal view #2484

reox opened this issue Oct 29, 2020 · 2 comments

Comments

@reox
Copy link
Contributor

reox commented Oct 29, 2020

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
If an attachment is inserted and the user switches immediately to the description view, the inserted attachment is not shown.

To Reproduce
Steps to reproduce the behavior:

  1. Open card in detached mode
  2. Click on edit
  3. insert some attachment
  4. switch back to view mode
  5. attachment is not shown
  6. switch into edit mode
  7. attachment is not shown in raw description either

Expected behavior
The edited text should be saved

Workaround
After inserting the attachment, write some text too.

NC 19.0.4 Deck 1.1.2
No error shown in JS console

@reox reox changed the title Inserted Attachments are not saved in detached view Inserted Attachments are not saved in modal view Nov 17, 2020
@reox
Copy link
Contributor Author

reox commented Apr 10, 2021

It looks like that since the update to NC 21.0.1 / Deck 1.3.2 this behaviour changed. The inserted image is now saved, but when switching back to "view description", it will not show up there. You have to wait ~3s until the description changes or click edit and view again.

@reox
Copy link
Contributor Author

reox commented Mar 22, 2022

It seems like this bug is fixed in 1.6.1, I can no longer reproduce the issue.

@reox reox closed this as completed Mar 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants