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

Minimize/maximize triangle icon small bug in the tree #14062

Open
Ruslan-Aleev opened this issue Aug 25, 2018 · 7 comments
Open

Minimize/maximize triangle icon small bug in the tree #14062

Ruslan-Aleev opened this issue Aug 25, 2018 · 7 comments
Labels
bug The issue in the code or project, which should be addressed. type-frontend Issues related to UI/UX issues, mostly about styles and frontend implementations on JavaScript.

Comments

@Ruslan-Aleev
Copy link
Collaborator

Ruslan-Aleev commented Aug 25, 2018

Summary

The icon appears in rows elements, resource folders and categories even if they are empty.
It's hard to understand are there row has any items until you click on all.

Step to reproduce

You can create an empty source of files, display it in the tree - the icon will appear, it will disappear when you click on the source, but if you refresh the page - it will appear again.

icon_bug

This behavior also happens in rows elements, resource folders, context and categories, perhaps
somewhere else.

MODX Revolution 2.6.5
Google Chrome 68.0.3440.106
Firefox 61.0.2

@OptimusCrime
Copy link
Contributor

This issue has been posted before. I was unable to find the duplicate. The reason for this is pretty simple, and the fix is pretty difficult. Basically, there is no way of knowing if the expand/collapse button should be displayed before you inspect the contents of the directory. This check has to be executed for each directory in the current directory you are browsing. One PR was prepared that fixed this, but the delay the fix introduced led to it being declined for inclusion. For S3 buckets especially, the latency added was very noticable.

Based on that, I think this is an issue we have to live with, unless we have changed our minds since then.

@Jako
Copy link
Collaborator

Jako commented Aug 26, 2018

@OptimusCrime Could that check run only on local file sources?

@OptimusCrime
Copy link
Contributor

Here is the original issue #13166 and PR #13337.

@Ruslan-Aleev
Copy link
Collaborator Author

@OptimusCrime Thanks for the detailed answer, I now understand the logic of the menu, speed is more important :)
p.s. I should close the issue, or leave it open, can someone notice and offer a non-standard solution?

@OptimusCrime
Copy link
Contributor

Lets see if someone "in charge" has something to say 😄

Just leave it open for now.

@alroniks
Copy link
Collaborator

We can leave it open but the fix should be provided only for local file systems as Mark suggested in discussions here #13337. Also, performance results should be provided.

@Ruslan-Aleev
Copy link
Collaborator Author

@alroniks Then should visually identify non-local sources: add some symbol (with Title attribute), color or icon to the non-local source in the header - otherwise it's very difficult to understand the logic to minimize/maximize, will seem like an obvious bug.
Maybe visually identify already done, did not use non-local sources.

Or leave everything as is :)

@JoshuaLuckers JoshuaLuckers added type-frontend Issues related to UI/UX issues, mostly about styles and frontend implementations on JavaScript. bug The issue in the code or project, which should be addressed. labels Mar 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue in the code or project, which should be addressed. type-frontend Issues related to UI/UX issues, mostly about styles and frontend implementations on JavaScript.
Projects
None yet
Development

No branches or pull requests

5 participants