What happened?
Dragging a file from Finder into the chat composer does nothing.
There is no visual feedback, no error, and the file path is not inserted into the input. From a user perspective this looks broken because the drag gesture is accepted by the window but silently ignored.
Expected behavior
When I drag a file into the composer, Paseo should insert the absolute file path into the prompt input so I can reference the file directly in my message.
At minimum, if non-image files are intentionally unsupported for drag-and-drop, the UI should surface that clearly instead of failing silently.
Steps to reproduce
- Open the Paseo desktop app.
- Open any chat/composer.
- Drag a local file from Finder into the message input area.
- Drop it onto the composer.
Actual result
Nothing happens.
Expected result
The dropped file path should be inserted into the composer text input.
Environment
- Platform: macOS desktop app
- Repo:
getpaseo/paseo
Notes
This may be related to the current drag/drop flow only handling image attachments and silently ignoring non-image files. Even if path insertion is considered a feature request rather than a bug, the current no-op behavior is confusing UX.
What happened?
Dragging a file from Finder into the chat composer does nothing.
There is no visual feedback, no error, and the file path is not inserted into the input. From a user perspective this looks broken because the drag gesture is accepted by the window but silently ignored.
Expected behavior
When I drag a file into the composer, Paseo should insert the absolute file path into the prompt input so I can reference the file directly in my message.
At minimum, if non-image files are intentionally unsupported for drag-and-drop, the UI should surface that clearly instead of failing silently.
Steps to reproduce
Actual result
Nothing happens.
Expected result
The dropped file path should be inserted into the composer text input.
Environment
getpaseo/paseoNotes
This may be related to the current drag/drop flow only handling image attachments and silently ignoring non-image files. Even if path insertion is considered a feature request rather than a bug, the current no-op behavior is confusing UX.