not intuitive to use contents on parent to perform actions on object

[djay]

Describe the bug

To delete, cut, rename etc an item you have to use "contents" and then navigate up (using the correct breadcrumb, not the public one) and then find the item again, select it and then you can do actions on it.

Proposed solution

Contents lets you select current item

The top row should represent the parent and you should be able to select it and perform actions on it. It should be clear this is the current object and everything else is underneath it

Other solutions considered

In edit sidebar

Could make sense to delete during edit. You can already rename during edit. You should be able to "move" an item during edit in the same way you can rename it during edit. It also makes sense to change workflow during edit.

Actions toolbar menu

Like plone classic has

cons

• more clutter
• not much room on moble

[ichim-david]

Adding a proper label, what you propose is an enhancement for a current feature. I understand you want it to behave differently but you didn't find a bug, you simply found something that you want to behave differently.

[djay]

Your opinion but to me bad UX is a bug. It's not a feature request to say something that doesn't work well should be fixed

On Sat, 1 June 2024, 12:48 pm ichim-david, @.***> wrote:

Adding a proper label, what you propose is an enhancement for a current feature. I understand you want it to behave differently but you didn't find a bug, you simply found something that you want to behave differently.

— Reply to this email directly, view it on GitHub https://github.com/plone/volto/issues/6061#issuecomment-2143309086, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAKFZANQG4LBKSZLPYIHKLZFFOC7AVCNFSM6AAAAABIRE4POSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTGMYDSMBYGY . You are receiving this because you authored the thread.Message ID: @.***>

[ichim-david]

Your opinion but to me bad UX is a bug. It's not a feature request to say something that doesn't work well should be fixed … On Sat, 1 June 2024, 12:48 pm ichim-david, @.> wrote: Adding a proper label, what you propose is an enhancement for a current feature. I understand you want it to behave differently but you didn't find a bug, you simply found something that you want to behave differently. — Reply to this email directly, view it on GitHub <#6061 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAKFZANQG4LBKSZLPYIHKLZFFOC7AVCNFSM6AAAAABIRE4POSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTGMYDSMBYGY . You are receiving this because you authored the thread.Message ID: @.>

@djay I can say the same thing, it's your opinion it's a bug but not mine. To quote: "A software bug is a problem causing a program to crash or produce invalid output". You propose for a feature to work in another way or todo something extra. There is no bug in the current implementation, there is just an enhancement to a currently working solution that you desire. Please keep the bug label for reproducible bugs and the enhancement label for improvements or changes you want to see happen, ideally followed also by a pull request if this request gains traction from the community.

[djay]

No it is not an opinion. If you are stating that the current way to delete something is desirable for some and not for others then I think you need to spend more time editing content using volto. You can argue that bug should refer to something tighter definition in your mind but there is no question in my my mind this is a UX bug in the true definition.

https://webapphuddle.com/what-is-a-ux-bug/#:~:text=In%20not%20so%20exact%20words,experience%20is%20a%20UX%20bug.

[ichim-david]

@djay ux label was also available for you to use. I am not saying I disagree with your assessment that things should behave differently because currently, it's too cumbersome. By definition saying that you don't like the fact that you have todo extra steps and you propose something else means that you want an enhancement to the contents component.

There are several options you have at your disposal:

1. Modify current contents logic with your vision
2. Join forces with Redturle and enhance https://github.com/collective/volto-contents-next
3. Wait for someone else to improve the content functionality story Up to you on which path you want to go from this point, I suggest you use the ux label and the enhancement label for the behavior you want to be changed but isn't a bug. Enhancement doesn't mean feature request, it means that something works in a way and it needs to be enhanced to work possible in another way.

[github-actions[bot]]

Hi There! 👋

We haven't seen any activity on this issue in a while :sleeping:, and we want to make sure that it's still relevant.

If updating to the latest version of Volto doesn't help, please let us know by:

• adding a comment about what needs to be done next 💬
• updating its status and other labels 🏷️

Otherwise close this issue. 🧹

[djay]

Another way to solve this is to make it possible to select the current object in the contents. Probably in this menu.

• how to show to the user its the current object selected
• can you act on the current and subobjects at the same time?

Pros

• don't clutter sidebar. esp good for mobile
• its where you go to do those actions on sub objects anyway so it somewhat intuitive
• easier implimentation.

Cons

• going to "contents" to act on the current context is confusing?

[djay]

or another way is: when clicking on the parent in the breadcrumbs it will automatically show the parent (paging if needed) and select it.