You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use the media viewer feature of the file explorer to manage my photos. I add tags and comments, so I can search and filter my photos later (e. g. show me all files tagged with "beach"). In another scenario I add comments to media files, so I can asynchronously communicate with other users of a Nextcloud instance (e. g. discuss mockups or blog post drafts).
However, I realized that the content of the viewer and the content of the sidebar are not in sync:
First, when you open picture A, and show the sidebar, you can add tags and comments etc. for picture A. When you switch to picture B in the viewer, the sidebar does not change but still shows tags and comments of picture A.
Steps to reproduce
Create a folder and add some images
Open the first image ("picture A") in the viewer
Show the sidebar
In the viewer, switch to the next or previous file ("picture B")
I use the media viewer feature of the file explorer to manage my photos. I add tags and comments, so I can search and filter my photos later (e. g. show me all files tagged with "beach"). In another scenario I add comments to media files, so I can asynchronously communicate with other users of a Nextcloud instance (e. g. discuss mockups or blog post drafts).
However, I realized that the content of the viewer and the content of the sidebar are not in sync:
First, when you open picture A, and show the sidebar, you can add tags and comments etc. for picture A. When you switch to picture B in the viewer, the sidebar does not change but still shows tags and comments of picture A.
Steps to reproduce
Screencast
https://youtu.be/i28S-FeizMY
Expected behaviour
Sidebar also updates its content to show tags and comments of picture B.
Actual behaviour
Sidebar keeps showing content (e. g. tags and comments) of picture A.
The text was updated successfully, but these errors were encountered: