[Bug] Canvas mouse input intermittently stops completely on Windows 11

### Prerequisites

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

### What happened?

On Windows 11, mouse interaction with the ComfyUI canvas intermittently stops working completely.

When the issue occurs:

- Right-clicking the blank canvas or a node does nothing. The context menu never opens.
- Double-clicking the blank canvas does nothing. The node search menu never opens.
- Sometimes normal left-click actions also stop responding.
- The mouse cursor may remain as a crosshair.
- The backend remains running and the page is not completely frozen.
- The problem may remain for approximately 10–20 minutes and then recover by itself without restarting ComfyUI or refreshing the page.

This is not just a case of needing to click multiple times. While the issue is active, right-click and double-click can remain completely non-functional.

I tested the following, but none of them consistently fixed the problem:

- Microsoft Edge and Google Chrome
- Incognito/InPrivate mode
- All browser extensions disabled
- Browser hardware acceleration disabled
- An external mouse and the laptop touchpad
- A blank workflow
- Starting ComfyUI with `--disable-all-custom-nodes`
- Resetting the ComfyUI user settings
- Dispatching synthetic `pointercancel`, `pointerup`, and `mouseup` events in DevTools

The pointer reset reached `LGraphCanvas` and logged `Pointer cancel!`, but mouse interaction did not recover.

My default bundled frontend is 1.45.21. During one attempted test with frontend 1.43.17, GitHub API rate limiting caused ComfyUI to fall back to 1.45.21, and the issue was still present.

After frontend 1.43.17 was successfully loaded from the local frontend directory, interaction was normal at that time. Since the problem is intermittent, I cannot yet confirm that frontend 1.45.21 is the sole cause, but the frontend version currently appears to be correlated with the issue.

### Steps to Reproduce

There are currently no fully deterministic reproduction steps because the issue is intermittent.

1. Start ComfyUI on Windows 11.
2. Open a workflow or use a blank canvas.
3. Interact with the canvas normally for some time.
4. At an unpredictable point, canvas mouse input may stop working.
5. Right-click the blank canvas or a node: no context menu appears.
6. Double-click the blank canvas: the node search does not appear.
7. In some occurrences, normal left-click actions also stop responding.
8. Leave the page open without restarting it. In some cases, interaction recovers by itself after approximately 10–20 minutes.

The issue has occurred across different browsers and input devices. I have not yet identified a specific workflow action that triggers it.

### How is this affecting you?

Feature doesn't work as expected

### ComfyUI Frontend Version

1.45.21

### Browser

Edge

### Console Errors

```javascript
No consistent red ComfyUI frontend exception appears when the issue occurs.

The following warning was repeatedly observed:

LGraphNode.ts:993 node onSerialize shouldn't return anything, data should be stored in the object passed as the first parameter

The related call stack included:

LGraph.serialize @ rgthree.js
app.graph.serialize @ quick_group_navigation.js
captureCanvasState @ changeTracker.ts

I do not know whether these serialization warnings are related to the mouse interaction issue.

I also tested manually dispatching pointercancel, pointerup, and mouseup events. LGraphCanvas received the events, but mouse interaction did not recover.
```

### Logs

```shell
ComfyUI version: 0.28.3
Installed frontend package: 1.45.21

Normal frontend startup:

[INFO] comfyui-frontend-package version: 1.45.21
[INFO] [Prompt Server] web root: D:\ComfyUI-aki-v3\python\Lib\site-packages\comfyui_frontend_package\static

During one test, frontend 1.43.17 could not be initialized because of GitHub API rate limiting, so ComfyUI fell back to the default 1.45.21 frontend:

[INFO] Initializing frontend: Comfy-Org/ComfyUI_frontend@1.43.17, requesting version details from GitHub...
[ERROR] Failed to initialize frontend: 403 Client Error: rate limit exceeded
[INFO] Falling back to the default frontend.
[INFO] comfyui-frontend-package version: 1.45.21

On a later test, frontend 1.43.17 loaded successfully:

[INFO] Initializing frontend: Comfy-Org/ComfyUI_frontend@1.43.17, requesting version details from GitHub...
[INFO] [Prompt Server] web root: D:\ComfyUI-aki-v3\ComfyUI\web_custom_versions\Comfy-Org_ComfyUI_frontend\1.43.17
```

### Additional Context

### Environment

- OS: Windows 11, build 22631
- ComfyUI: 0.28.3
- Frontend where the issue was observed: 1.45.21
- Python: 3.13.11
- PyTorch: 2.9.1+cu130
- GPU: NVIDIA GeForce RTX 4060 Laptop GPU, 8 GB VRAM
- RAM: 32 GB

### Tests performed

I tested the following:

- Microsoft Edge and Google Chrome
- InPrivate/Incognito mode
- All browser extensions disabled
- Browser hardware acceleration disabled
- External mouse and laptop touchpad
- A blank workflow
- Resetting `comfy.settings.json`
- A new user directory
- Starting ComfyUI with `--disable-all-custom-nodes`

None of these consistently prevented or resolved the issue.

The problem has occurred approximately four or five times. It is intermittent and currently has no deterministic trigger. In some cases, the canvas starts working again by itself after approximately 10–20 minutes without restarting ComfyUI.

During one session where the local frontend 1.43.17 was definitely loaded, mouse interaction worked normally. However, because the issue is intermittent, I cannot yet conclude that frontend 1.45.21 is the sole cause.

The issue is more severe than unreliable double-click detection: while it is active, right-click and double-click do not work at all, and some normal left-click actions may also stop responding.

Start by comparing frontend versions 1.45.21 and 1.43.17 while observing the intermittent failure, then inspect pointer handling around LGraphCanvas. Review the reported LGraphNode.ts:993 warning and the call path through changeTracker.ts and quick_group_navigation.js without assuming they are causal. Done means identifying a reproducible trigger or confirmed cause and covering the corrected behavior with a regression test.

Written by the indexing model from the issue text.