-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't listen dom events on dom type node #3342
Comments
Hi @krishna-fenixwork ,
|
Hi, @cliffordfajardo thank you for the quick response. I've updated the code block in the description so you can understand it better. I've also added the code on stackblitz to reproduce the problem, please have a look. https://stackblitz.com/edit/nextjs-g3cshp About Graphin, yes I heard about that and used it on one of my react project but on next js using graphin gives me error. You can find the graphin related issue on next js here - https://github.com/antvis/Graphin/issues/250 It'd be better if we can use graphin on next js too. |
How about customizing node with react tags instead of dom node? refer to https://g6.antv.vision/en/docs/manual/middle/elements/nodes/react-node/ |
Hey, @Yanyan-Wang, I tried g6-react-node also. But, I'm not able to use JSX or HTML in it. It throws a run-time error while using JSX or HTML tag instead of using tags of its library. What about if I want to make my custom node editable or want to put a textbox inside that or a slider and get its value on change. Can we do that using your recommended link? https://g6.antv.vision/en/docs/manual/middle/elements/nodes/react-node/ If you know something related to my use case, please help me. |
This issue has been closed because it has been outdate for a long time. |
I'm using next js. I'm writing this binding function after graph.render so we can get dom event. But, I can't be able to listen the input event on input type text added on the dom node. Can anyone help me with this? Is there any other way to add html or react component to node and handle events?
The text was updated successfully, but these errors were encountered: