wailsapp
[v3] Drag and drop broken in v3.0.0-alpha.36+ due to go-webview2 v1.0.22 upgrade
Description
Drag and drop functionality is completely broken starting from Wails v3.0.0-alpha.36 on Windows. The application builds and runs, but all drag-and-drop zones fail to register with the following error:
ERR error registering drag and drop: Not enough memory resources are available to complete this operation.
This issue was introduced by the go-webview2 library upgrade from v1.0.21 to v1.0.22 in PR #4645.
To Reproduce
- Create a Wails v3 application with drag-and-drop zones (or use any existing app with DnD)
- Update to Wails v3.0.0-alpha.36 or later:
go get github.com/wailsapp/wails/[email protected] - Run the application
- Observe the console output showing repeated errors:
Nov 10 12:51:27.274 ERR error registering drag and drop: Not enough memory resources are available to complete this operation. - Attempt to drag and drop files into the application - functionality will not work
Expected behaviour
Drag and drop zones should register successfully without errors, and files should be droppable into the application as they were in v3.0.0-alpha.35 and earlier
Screenshots
No response
Attempted Fixes
Tested v3.0.0-alpha.35 (with go-webview2 v1.0.21) - ✅ drag and drop works correctly Tested v3.0.0-alpha.36 (with go-webview2 v1.0.22) - ❌ drag and drop fails with error Tested v3.0.0-alpha.38 (with go-webview2 v1.0.22) - ❌ drag and drop fails with error
System Details
Wails (v3.0.0-alpha.38) Wails Doctor
# System
┌──────────────────────────────────────────────────────────────────────────────┐
| Name | Windows 10 Pro |
| Version | 2009 (Build: 26200) |
| ID | 25H2 |
| Branding | Windows 11 Pro |
| Platform | windows |
| Architecture | amd64 |
| Go WebView2Loader | true |
| WebView2 Version | 142.0.3595.53 |
| CPU | AMD Ryzen 5 5600X 6-Core Processor |
| GPU 1 | NVIDIA GeForce RTX 3070 (NVIDIA) - Driver: 32.0.15.8180 |
| Memory | 32GB |
└──────────────────────────────────────────────────────────────────────────────┘
# Build Environment
┌─────────────────────────────────────────────────────────────────────────────────────────────────────┐
| Wails CLI | v3.0.0-alpha.38 |
| Go Version | go1.25.3 |
| -buildmode | exe |
| -compiler | gc |
| CGO_ENABLED | 0 |
| DefaultGODEBUG | containermaxprocs=0,decoratemappings=0,tlssha1=1,updatemaxprocs=0,x509sha256skid=0 |
| GOAMD64 | v1 |
| GOARCH | amd64 |
| GOOS | windows |
└─────────────────────────────────────────────────────────────────────────────────────────────────────┘
# Dependencies
┌────────────────────────────────────────────┐
| npm | 10.9.4 |
| NSIS | Not Installed |
| MakeAppx.exe (Windows SDK) | Not Installed |
| MSIX Packaging Tool | Not Installed |
| SignTool.exe (Windows SDK) | Not Installed |
| |
└───────── * - Optional Dependency ──────────┘
# Checking for issues
SUCCESS No issues found
# Diagnosis
SUCCESS Your system is ready for Wails development!
Need documentation? Run: wails3 docs
♥ If Wails is useful to you or your company, please consider sponsoring the project: wails3 sponsor
Additional context
No response
That's so weird as I specifically tested it on Windows using the new example. Thanks for reporting.
Hey, I have experienced similar issue with recent versions of v3-alpha branch and I have submited a PR #4765 with my fix. It works, at leas for me. Any feedback welcome.
@xob0t - The above PR is merged. If that doesn't fix this, please reopen 🙏