We are experiencing an issue when editing the Title and Alt Text of an existing image.
When an image is uploaded, we can enter a Title and Alt Text and save them successfully. However, when the image is used later and we try to edit or correct one of these values, the existing text disappears as soon as we click into the text field.
This means that instead of being able to edit the existing value — for example, to correct a typo — the entire Title or Alt Text has to be entered again.
Steps to reproduce
Upload an image.
Enter a Title and Alt Text.
Save the image.
Use/select the image in a record.
Try to edit the existing Title or Alt Text.
Click into the text field.
The existing value disappears completely.
Expected behavior
The existing Title and Alt Text should remain in the fields and be editable, so that individual words or typos can be corrected without having to re-enter the entire value.
Actual behavior
As soon as the field is clicked, the existing value disappears and has to be entered again from scratch.
According to our client, it was previously still possible to edit the Alt Text without losing its value. Now the issue seems to affect both Title and Alt Text.
Sorry, I investigated this further, and I misunderstood your original screenshot.
What I think is happening is actually something different…
If you set your title & alt text inside the media area, they become the default values for that asset.
However, optionally, you may choose to override those defaults by overwriting them on a specific field. If you don’t, then we will just use the defaults that you set in the media area.
So what you’re seeing here is maybe just the UI not being clear enough… if your client wants to edit the text they previously did, they should open that asset in the media area first, and then edit it there (as opposed to apply a field-level override, which is what they’re doing here). Does that make sense?
Thanks, that makes sense from a technical perspective!
I think the issue for us is more about the UI/UX then. From the client’s perspective, they see the existing Title or Alt Text in the field and naturally assume they can click into it and make a small correction. When the text disappears on click, it gives the impression that the existing value has been lost and that they need to enter everything again.
The distinction between the default value from the media area and a field-level override isn’t really clear from the UI, especially for non-technical users. The client doesn’t necessarily know or care where the value is stored — they just see a value and expect to be able to edit it.
So perhaps the inherited/default value could remain visible when starting an override, or the UI could make it clearer that the displayed value is inherited from the asset and that editing it here creates an override. I think either approach would make the behavior much clearer for users.
