C4 multiple edit/delete menu backend not comfortable

[eBlick]

I didn't finde any information why the edit/delete/copy menu in multiple edit mode is so uncomfortable.
First I don't see any reason to put these options into a dropdown, while there is so much space around (two clicks necessary), second If there ist a reason for this, why do we have the "delete" option priorized on top?
I use the copy, or overwrite option much more often and I believe that other users do this, too.
I regularly click on the delete option by accident when I miss the dropdown arrow.

If you please get rid of the dropdown or at least put the "copy" option on top.

[OMOSde]

For Contao 4.4+ you can use the upcoming version 1.2 from https://github.com/OMOSde/contao-om-backend. There is an option in the user settings to remove the submenus for save and edit multiple buttons.

[Samson1964]

+1

[Toflar]

Yeah there's general consent about that. The thoughts behind this are easy to understand: If you're on mobile you don't have that much space for 6 buttons, that's why there are only two or three and the rest is in a dropdown. The best way would be to make it responsive but nobody worked on that so far. If you could do that, we'd be very happy to integrate that solution :)

[leofeyer]

Yeah there's general consent about that.

Is there? I find myself using the "delete" option a lot more than the copy option, so I'm -1 on making "copy" the top option.

The best way would be to make it responsive but nobody worked on that so far.

I once tried to change it, however, the stacked button requires a certain HTML markup with a surrounding container, so we cannot simply take buttons out of the stack with only CSS.

[OMOSde]

CSS only, could be possible. I do it here: https://github.com/OMOSde/contao-om-backend/blob/master/src/Resources/public/css/om_backend.css#L152-L191

But, not very well tested.

[Toflar]

Is there?

Yeah, about using the space on desktop if it's there. Not about the order of the buttons obviously (I don't care about that anyway).

[fritzmg]

I once tried to change it, however, the stacked button requires a certain HTML markup with a surrounding container, so we cannot simply take buttons out of the stack with only CSS.

Shouldn't be that difficult without changing the current markup even. This is just crude reconstruction: https://jsfiddle.net/de7vj417/

[leofeyer]

The goal is not to deconstruct the stacked button completely, but to extract single buttons depending on the browser width.

[fritzmg]

I see. But is that goal really necessary? Wouldn't it be more important to have at least have one breakpoint at which at least all buttons are visible?

[leofeyer]

I don't think that seven buttons next to each other is a good UX decision.

[fenepedia]

What about adding an custom user option, so everybody could set the default value?

[JLBA]

Contrary to Leo, I think users need to see anytime what they can do and catch buttons quickly (one click). Hiding buttons in one dropdown menu can be a solution on smartphones. On computers or tablets, it's just a foolish search of absolute flat purity design initiated by Apple (followed by Google) who was better inspired in 1984 ;-)

[leofeyer]

Changed in contao/core-bundle@bfe804e then.