Skip to content
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

Usability? How to refocus current node in tree after "Collapse All" #3805

Open
mhsdesign opened this issue Jun 16, 2024 · 5 comments
Open

Usability? How to refocus current node in tree after "Collapse All" #3805

mhsdesign opened this issue Jun 16, 2024 · 5 comments

Comments

@mhsdesign
Copy link
Member

mhsdesign commented Jun 16, 2024

#3756 introduced a new collapse button in the document tree:

image

but after collapsing its unclear how to find the current node again in the tree.

image

For that to achieve i have to reload the tree but i think we are missing a more dedicated feature for that.

image image

PHPStorm for example faces a similar problem and thus offers a target button to highlight the current file again:

image

I think we should consider such option as well

@lorenzulrich
Copy link
Contributor

@mindpilot Do you have an opinion on this?

@mhsdesign
Copy link
Member Author

or as-well @Devclaim ? ;)

@ahaeslich
Copy link
Member

@laurahaenel and me discussed this feature on friday as well. This would not just be a good idea if an editor collapsed everthing but also, wenn they did this manually for a deep subtree folder they are currently located at.

@mindpilot
Copy link

Hi @mhsdesign , having a button "show in page in document tree" which opens and highlights the current page, would be quite handy.

neos-target-button

What I'm still missing is the permanent storage of manually collapsed menu items over time. Editors on large sites very often are working on a limited set of pages all the time. For thus having the same tree state upon the next session would be helpful.

@Devclaim
Copy link
Contributor

Devclaim commented Jul 1, 2024

I like the Idea and will look into it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants