-
Notifications
You must be signed in to change notification settings - Fork 452
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
Unable to drag/reposition nodes in Brave (Chromium) #827
Comments
As this is specifically about the layout editor included with Node-RED dashboard, I'll move this issue over to that project. |
My fault @knolleary - when explained in Slack I read this as not being able to drag the nodes in the Node-RED Editor, so asked to raise here. |
Yeah - the gridstack library we use was evolved really quickly after we adopted it, and they have broken their API multiple times since. (now v10.0 vs our v0.6). Last time I tried to update it, it broke a whole bunch of other stuff, and needed other support, so I have just pinned it back. The reality is that I am unlikely to ever fix this as we are slowly moving over to Dashboard2, but if anyone wants to have a go please jump in and do so, as it would be much appreciated. |
Is Dashboard2 available for use? |
It most certainly is: https://dashboard.flowfuse.com/ Not 100% feature parity yet, but most of it (plus some new stuff) is in there |
Awesome! I really like that you're using Vue3... good stuff. FWIW, I'm cool with closing this. :) |
Current Behavior
In Node-RED v3.1.3 using node-red-dashboard 3.6.2, it’s apparently not possible to drag/reposition nodes around using the latest Brave Browser (on Mac; v1.61.114 Chromium: 210.0.6099.199). Brave's "shields" are down. I tried clearing cache. No interesting errors in console when trying to select/drag.
Doing the same thing from the same server using Safari works as expected.
safari--working.mp4
brave--not-working.mp4
Expected Behavior
Dragging nodes should work as seen in the Safari video
Steps To Reproduce
No response
Example flow
Environment
The text was updated successfully, but these errors were encountered: