I made a bunch of changes. I tried a bunch of builds, but nothing I did solved the problem. Wails' native OnFileDrop callback isn't triggering at all. According to my research, there's a WebView2/Wails compatibility issue, and Wails v3 has fixed these problems, but it's still in alpha. Classic Windows cancer.
Until Wails v3 reaches a more stable version, a temporary UI-based file selector can be used.
There was a serious drag & drop issue in Wails v3.0.0-alpha.36+ versions:
“Not enough memory resources” error
It appeared with the update of the go-webview2 library to v1.0.22
Many fixes were made in Wails v3.0.0-alpha.56 (January 2026):
Non-100% screen scaling issues on Windows were fixed
HTML5 internal drag & drop issues were resolved
File drop coordinates were fixed
API Changes (v3.0.0-alpha.56+):
EnableDragAndDrop → Renamed to EnableFileDrop
data-wails-dropzone → Changed to data-file-drop-target
WindowDropZoneFilesDropped → Changed to WindowFilesDropped
I made a bunch of changes. I tried a bunch of builds, but nothing I did solved the problem. Wails' native OnFileDrop callback isn't triggering at all. According to my research, there's a WebView2/Wails compatibility issue, and Wails v3 has fixed these problems, but it's still in alpha. Classic Windows cancer.
Until Wails v3 reaches a more stable version, a temporary UI-based file selector can be used.
There was a serious drag & drop issue in Wails v3.0.0-alpha.36+ versions:
“Not enough memory resources” error
It appeared with the update of the go-webview2 library to v1.0.22
Many fixes were made in Wails v3.0.0-alpha.56 (January 2026):
Non-100% screen scaling issues on Windows were fixed
HTML5 internal drag & drop issues were resolved
File drop coordinates were fixed
API Changes (v3.0.0-alpha.56+):
EnableDragAndDrop → Renamed to EnableFileDrop
data-wails-dropzone → Changed to data-file-drop-target
WindowDropZoneFilesDropped → Changed to WindowFilesDropped