Make it easier to jump between tree and comment(s)

[philippotto]

If a user has lots of trees and lots of nodes with comments, it can be cumbersome to scroll to the correct counter part. The two cases are:

• I have clicked on a comment in the comment tab and now I want to scroll to the corresponding tree in the trees tab
• I have clicked on a tree in the skeleton tab and now I want to scroll to the corresponding comments in the comments tab

Ideas

A) Automatically expand/scroll to the corresponding counter part. Note that both tabs CAN be visible at the same time but it cannot be assumed. Both cases should work.
B) Add a "go to tree/comments" item to the context menu. Then the other tab could be activated and the relevant item would be focused.

Approach

We should check first what the status quo is for the described use cases. Then, we should find out which solution is the best way to go.

Todos

• changing active tree should clear "selected tree ids" even when tree tab is invisible
• when activating tree tab, it should scroll to active tree
• "focus tree" should also work if the tree is already active (possibly difficult because react component needs to listen to action or sth similar)
• "focus tree" should also activate tree tab if it is not already visible

Context

https://scm.slack.com/archives/C5AKLAV0B/p1747294069361719

[knollengewaechs]

I think there might be a problem in the skeleton tab.

A) seems to be working already if both tabs are open at the same time. Right now, when clicking on a comment from the comments tab, the corresponding node is activated. If the skeleton tab is open, the right node is centered. But if the skeleton tab is not active, the active node does not update, leading to an inconsistent state when the tab is reopened.
Vice versa, this problem does not occur, the comments seem to be in sync with the active node, even if the tab is in the background/closed when the new active node is set.

Thus I propose that I'll try to fix the problem in the skeleton tab first?

[hotzenklotz]

@knollengewaechs What about this issue? The PR is merged. Can the issue be closed as well?

[knollengewaechs]

this issue is still open because of "focus tree" should also activate tree tab if it is not already visible". My intention was to have a further look at how this could be done