useOnSelectionChange never fires
See original GitHub issueDescribe the Bug
I am attempting to use the examples for <ReactFlowProvider>
and useOnSelectionChange
but never get the selection change to fire
Your Example Website or App
https://codesandbox.io/s/green-worker-pz6fvj?file=/src/App.tsx
Steps to Reproduce the Bug or Issue
The console should print the selected node. I can tell the node is selected because the border is thicker…
Expected behavior
I expect the console to fire with the selected node
Screenshots or Videos
No response
Platform
- OS: macOS
- Browser: Chrome
- Version: 105
Additional context
No response
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Workaround: <Select>ing the first <option> never fires an ...
Note: I'm aware that the standard answer to the "First selection doesn't generate onchange events" problem is to make a dummy (disabled) first ......
Read more >HTMLInputElement: selectionchange event - Web APIs | MDN
The selectionchange event of the Selection API is fired when the text selection within an <input> element is changed.
Read more >The attribute for input tag"onchange" will not fire, but ...
When I type something into the input, validateNumberInput will not fire. However if I use onkeydown, it will fire. Am I missing something...
Read more >SCR19: Using an onchange event on a select element ... - W3C
The objective of this technique is to demonstrate how to correctly use an onchange event with a select element to update other elements...
Read more >onChange event not firing · Issue #3426 · ianstormtaylor/slate
onKeyDown fires correctly, but onChange never fires. Others on the slack channel have also come across this bug, and state the only solution ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is a bug! Will be fixed tomorrow 😃 Thanks for the report.
fix released in v11.1.1