Feature #97043
open
Replace IRRE image while retaining text and links
0%
Files
Updated by Christian Toffolo over 2 years ago
- File Untitled Project.png Untitled Project.png added
- Subject changed from New button to replace the image while retaining text and links to Replace IRRE image while retaining text and links
Add a new button to replace IRRE image while retaining text and links.
Updated by Georg Ringer over 2 years ago
- Status changed from New to Needs Feedback
Thanks for creating this issue. While this might look easy in the first run, this would lead to lots of decisions which need to be made but are totally unclear. An example is the cropping information which is also persisted in the reference. should those be kept or removed as well?
Updated by Christian Toffolo over 2 years ago
I propose to ask the user "Keep cropping information?" (only if the cropping is set) at the time of replacement.
What are the other decisions to make that come to your mind?
Updated by Christian Toffolo over 2 years ago
Or, like it happens replacing file in Filelist module (just tested in v10), cropping information is preserved. The editor then have to fix it eventually.
Updated by Christian Toffolo over 2 years ago
- Status changed from Needs Feedback to New
- Target version set to Candidate for Major Version
- Parent task set to #93528
Updated by Christian Toffolo over 2 years ago
- Related to Epic #93528: Backlog of UX ideas for Editors added
Updated by Riccardo De Contardi 7 days ago
- Related to Feature #95447: Edit file properties directly from where it is referenced added
Updated by Garvin Hicking 6 days ago
- Sprint Focus set to Needs Decision
Another idea was mentioned in the related #95447 - adding a "deeplink" to the filelist tree to perform the operation(s).
It might be hard to actually do that, because the filelist tree is paginated, and "jumping" to a file will be hard. It might be possible by performing a search on the filename in a specific directory. At least jumping to the directory of the file could be possible.
Sadly, for a deeplink into this, several other URI arguments (like "tile or list view") may be persisted and might need retrieval from the last-visit state. So this may get actually harder than you'd think in first instance.
Having said that - I think it would be very helpful for editors to be able to have this possibility to "go" to the originating file!