You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently using the included SVGViewer, but when using touch events like in mobile/tablet, it triggers infinite console errors and renders unusable click events like Match details and onPartyClick.
To Reproduce
Use the SingleEliminationBracket (might happen in the other one, but haven't checked), use the included Match component and SVGViewer. Then configure chrome to use touch events.
It seems to trigger errors but the scroll seems to work fine, but it seems to eliminate all click events like Match Details which can't be clicked.
Screenshots/Video
4872d91d65d16eba253040c8a4fb1fd5.mp4
Versions
react-tournament-brackets ^1.0.30
React ^18.2.0
Node v16.18.0
Conclusion
It seems like a SVGViewer problem since I have checked and it can be configured in the original library. But I was wondering if someone has encountered this before and has a way to fix it only using the provided components or if there is plan to include it out of the box.
Thanks!
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm currently using the included SVGViewer, but when using touch events like in mobile/tablet, it triggers infinite console errors and renders unusable click events like Match details and onPartyClick.
To Reproduce
Use the SingleEliminationBracket (might happen in the other one, but haven't checked), use the included Match component and SVGViewer. Then configure chrome to use touch events.
Code
Priority
It seems to trigger errors but the scroll seems to work fine, but it seems to eliminate all click events like Match Details which can't be clicked.
Screenshots/Video
4872d91d65d16eba253040c8a4fb1fd5.mp4
Versions
Conclusion
It seems like a SVGViewer problem since I have checked and it can be configured in the original library. But I was wondering if someone has encountered this before and has a way to fix it only using the provided components or if there is plan to include it out of the box.
Thanks!
The text was updated successfully, but these errors were encountered: