事件监听

Description

1、版本v2.10
2、 windows10
3、描述： 后端 EventsEmit 前端 EventsOn 无效
后端代码

前端代码

To Reproduce

后端代码

前端代码

Expected behaviour

前端能监听到数据

Screenshots

No response

Attempted Fixes

No response

System Details

# Wails
Version | v2.10.1


# System
┌────────────────────────────────────────────────────────────────────────┐
| OS           | Windows 10 Pro                                          |
| Version      | 2009 (Build: 19045)                                     |
| ID           | 22H2                                                    |
| Go Version   | go1.24.1                                                |
| Platform     | windows                                                 |
| Architecture | amd64                                                   |
| CPU          | Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz               |
| GPU          | NVIDIA GeForce GTX 1650 (NVIDIA) - Driver: 32.0.15.6094 |
| Memory       | 16GB                                                    |
└────────────────────────────────────────────────────────────────────────┘

# Dependencies
┌───────────────────────────────────────────────────────┐
| Dependency | Package Name | Status    | Version       |
| WebView2   | N/A          | Installed | 137.0.3296.68 |
| Nodejs     | N/A          | Installed | 20.17.0       |
| npm        | N/A          | Installed | 10.8.2        |
| *upx       | N/A          | Available |               |
| *nsis      | N/A          | Installed | v3.11         |
|                                                       |
└─────────────── * - Optional Dependency ───────────────┘

# Diagnosis
Optional package(s) installation details:
  - upx : Available at https://upx.github.io/

 SUCCESS  Your system is ready for Wails development!

 ♥   If Wails is useful to you or your company, please consider sponsoring the project:
https://github.com/sponsors/leaanthony

Additional context

No response

Start by reproducing the reported EventsEmit-to-EventsOn failure in the Wails v2.10.1 Windows 10 environment described in the issue. Inspect the backend and frontend event usage shown in the attached examples, then verify whether the frontend receives the emitted data. Done means the reported event is reliably received by the frontend, with a regression test or documented reproduction if the relevant test location is identified.