SpecterOps
Feature: Disable Double Click to Zoom
Feature Description
I'm currently reviewing a massive AD with 25K+ users, using the "Shortest paths to Domain Admin" results in lots of uncollapsed nodes making the graph absolutely massive, which means I need to move around a LOT to see what the original path was in order to retain the text on the screen.
When dragging around the graph, I keep repeatedly triggering the double-click to zoom feature, which gets incredibly annoying as all I'm trying to do is just navigate upwards/downwards, but the new BloodHound UI keeps zooming in so I end up just zooming out every time.
Are you intending to implement this feature?
I can try, but I have no clue where to start to be honest. If it's an easy fix for you guys it would be appreciated otherwise I can see what I can do
Current Behavior
drag, drag, (auto zooms in), (scrolls to zoom out), drag, drag, (auto zooms in), (scrolls to zoom out)
Desired Behavior
drag, drag, drag, drag, drag, drag, drag, drag
Use Case
Better UX, it's very frustrating to navigate around large graphs at the moment. This might be intuitive on touch devices like iPads, but on desktop PC's / laptops (which most pentesters will be using) it's more logical that if they want to zoom they'll just use the scroll wheel
Implementation Suggestions
It would be appreciated if the graph either disables double-click to zoom by default, or has a button that disables this behavior in the graph.
Additional Information
Fixing https://github.com/SpecterOps/BloodHound/issues/89 would also partially solve this issue as BloodHound CE produces humongous graphs compared to ye olde BloodHound. Maybe clustering nodes a little closer together would also help out, as it sometimes places nodes very far away from the other nodes.
Hi @Paradoxis, thanks for reporting this! I can definitely see the frustration here.
While digging into this, we noticed that this behavior is actually different between BHE and BHCE so this may be unintended. With that said, we're always hesitant to remove functionality. Just wanted to let you know that we're trying to determine the best path forward for this 😄
Ah that would explain a lot :) my colleagues and I were already confused by this behavior, if there’s anything I can do to help please do let me know
@Paradoxis Thank you again for the report!
Just got the fix merged into main. Unfortunately, due to the holiday, this won't make it into the product until our release cadence picks back up in the new year. That should be mid to late January. Hopefully it's not too big of a pain until then 😃