Comfy-Org / Comfy-Org/ComfyUI_frontend

Regression: Drag and drop from Media Assets panel into file explorer broken

Open
#12,314 2 comments 1 reaction 0 assignees View on GitHub
browser:firefox platform:windows Potential Bug
Dominant language
TypeScript
Stars
2k
Forks
699
Avg merge
1d 7h
Merged PRs (30d)
490

Description

### Prerequisites

- [x] I am running the latest version of ComfyUI
- [x] I have custom nodes enabled

### What happened?

It seems that in newer versions of the frontend, I'm unable to drag an image from my media assets panel directly into my file explorer (windows). There seems to have been a recent behavioral change that causes the drag behavior to pick up the whole panel surrounding the image and not just the image itself. Consequently when dragged, the asset now acts like an http link, so depending on browser it will either copy nothing into Windows explorer or will create an http shortcut.

Here is what the drag behavior looks like on 1.42.15:
Image
Here is what the drag behavior looks like on 1.43.18 (note, the entire panel gets picked up by the cursor, not just the image):
Image

### Steps to Reproduce

1. Generate an image
2. Open Media Assets tab
3. Open Windows Explorer to the side.
4. Attempt to drag the image from Media Assets tab into a Windows Explorer folder.

### How is this affecting you?

Minor inconvenience

### ComfyUI Frontend Version

1.43.18

### Browser

Firefox

### Console Errors

```javascript

```

### Logs

```shell

```

### Additional Context

_No response_

┆Issue is synchronized with this [Notion page](https://www.notion.so/Issue-12314-Regression-Drag-and-drop-from-Media-Assets-panel-into-file-explorer-broken-3636d73d365081608697c3d0a4d2327f) by [Unito](https://www.unito.io)

Contributor guide

Open the contributing guide

Research direction

Start at the Media Assets tab and reproduce the drag from a generated image into Windows Explorer using Firefox. Compare the behavior between frontend versions 1.42.15 and 1.43.18; done means only the image is dragged and Windows Explorer receives the asset rather than an HTTP link or the surrounding panel.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.