Devtools breaks react-resizable-panels cursor after remount
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- electron, react, typescript
Research direction
Start with the StackBlitz reproduction, especially src/App.tsx and package.json, and reproduce the cursor failure after changing the Group key. Trace the Devtools and Solid event handling described in the issue, then determine whether the fix belongs here or upstream. Done means remounting leaves the separator cursor working without changing native event properties for unrelated listeners.
Written by the indexing model from the issue text.
Description
TanStack Devtools version
0.10.12
Framework/Library version
React 19.2.8
Describe the bug and the steps to reproduce it
With TanStack Devtools mounted, remounting a react-resizable-panels Group breaks its hover cursor.
Steps: render Devtools alongside a Group with two Panels and a Separator. Wait for Devtools to load, then change only the Group's key and hover the separator.
Confirmed locally in Electron using these minimal components:
- Initial mount: resize listener runs before Solid; cursor is
ew-resize. - After remount: Solid runs first; hover is detected, but cursor stays
auto.
Solid's delegated pointermove handler leaves event.currentTarget pointing to <html> instead of document. The resize library then skips cursor styling because currentTarget.defaultView is undefined.
Remounting is normal React behavior. Devtools should not change native event properties for unrelated listeners. Is this best addressed here or upstream in Solid?
Versions: @tanstack/react-devtools 0.10.12, solid-js 1.9.15, react-resizable-panels 4.12.3, React 19.2.8, Electron 44.1.0 (macOS).
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
https://stackblitz.com/edit/vitejs-vite-eha3ugdo?file=src%2FApp.tsx,package.json&terminal=dev
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
No, because I do not know how
Terms & Code of Conduct
- I agree to follow this project's Code of Conduct
- I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
- Dominant language
- TypeScript
- Stars
- 499
- Forks
- 100
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TanStack/devtools
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in TanStack/devtools
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dennys-bd/agent-hive#184 ·
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vicharanashala/fln#563 ·