Opened 8 years ago
Closed 4 years ago
#41465 closed defect (bug) (invalid)
Drag-and-drop image placement is confusing
Reported by: | mor10 | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 4.9 |
Component: | Media | Keywords: | reporter-feedback |
Focuses: | Cc: |
Description
When a user drags-and-drops an image onto the editor, the image placement is not obvious and the experience leaves users confused:
- At the start of the process, the text caret is somewhere in the text.
- on drag-and-drop, the add media panel appears abstracting the user from the task of placing the image in the correct context in the text.
- When the add image panel is exited by clicking "Add Image", the image appears where the cursor was originally placed.
The introduction of the abstraction layer of the Add Image panel causes the user to shift focus enough that the final location of the image placed in the text seems arbitrary.
Possible solutions:
- Allow the user to drag the image onto the canvas and place it in context by visualizing a placeholder container before the modal is opened. The modal should only open after placeholder placement is made so the user knows where they placed the image before dealing with metadata.
- If the sequence of events must start with the add media modal, allow the user to place the image within context after clicking Add image: Rather than the image being placed at the current caret position, show a placeholder with an interactive outline the user can drag around and position before the actual image is placed.
Image placement via drag-and-drop is an issue that shows up often in user testing. It is poorly understood and leads users to feel like WordPress is either acting at random or worse making decisions on their behalf.
Change History (5)
This ticket was mentioned in Slack in #core-media by joemcgill. View the logs.
6 years ago
This ticket was mentioned in Slack in #core-media by antpb. View the logs.
4 years ago
Note: See
TracTickets for help on using
tickets.
@mor10 does the new block editor solve this problem?