Closed behoyh closed 2 years ago
I was able to fix this by replacing all references to window
with this._baseRef
@behoyh awesome! are you able to put it into a PR?
Right now I'm trying to fix some placement issues, hopefully I'll be able to fix it soon.
EDIT: on second though I think passing in a ref for the parent element would be the best option.
Had a bit of a look into this today - No luck.
It seems that React portals use the same window
ref as the main DOM.
I'm going to attempt to fix this over the next few weeks, but it'll need a bit of research
I believe this is fixed in the above commit, feel free to reopen if anyone finds this is not the case - added a storybook with demo
Very cool - thank you!!
:tada: This issue has been resolved in version 4.0.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
@behoyh did it resolve the issue for you?
I don't have access to the codebase at this time so I cant say for certain.
Got an interesting issue for you. when using the joystick in a new window, it seems that the mouse move event binds to the parent window, and does not move from where the child window rendered the component.