Omar Ghazal
My feedback
1 result found
-
230 votes
InDesign 21.4.1, which includes the fix, is now live.
The update should be available in the Creative Cloud app. If you do not see it yet, please click “Check for Updates” to refresh the available updates.
Thank you for your patience and understanding while we worked to resolve this issue.
--
Adobe InDesign team
Omar Ghazal supported this idea ·
An error occurred while saving the comment
Possible Bug After Latest InDesign Update – Multi-Object Selection Lost When Dragging from Images
Hello Adobe Support,
I am experiencing a problem that started immediately after installing the latest InDesign update.
Issue Description:
When I select multiple objects on the page (for example, two image frames and two shape objects), the selection behaves unexpectedly when I try to drag the selected items.
Expected Behavior:
When multiple objects are selected, dragging from any selected object should move the entire selection.
Actual Behavior:
If I start dragging from a shape or text object, all selected objects move correctly.
If I start dragging from an image inside an image frame, the multi-selection is immediately canceled and only the image/frame becomes selected.
As a result, only that single image moves instead of the entire selection.
Additional Information:
The problem started immediately after updating InDesign.
The issue occurs even in new documents.
Moving the selected objects with the keyboard arrow keys works correctly and moves the entire selection.
Grouping the objects (Ctrl+G) allows them to move correctly.
The problem only occurs when dragging from image frames.
The issue did not exist before the update.
Troubleshooting Already Attempted:
Restarted InDesign.
Tested with new documents.
Verified that objects and layers are not locked.
Confirmed that the Selection Tool is being used.
Reset workspace.
Tested different object types.
This behavior appears to be related to how image frames or placed images are being handled after the latest update.
Could you please confirm whether this is a known issue or provide a workaround?
Thank you.