If accepted then this change would have to be made everywhere not just in this one component

If accepted then this change would have to be made everywhere not just in this one component

It's actually a Params.php File that appears to have effect in several components and I changed also the articles edit page which was seperate from the params.php

The PR is for the places where the automatic columns class was set.

I have tested this item ✅ successfully on 339380c

good now i see only one column
also works on a 17 "monitor bringing the browser with zoom to 30%

I have tested this item ✅ successfully on 339380c

RTC

Can we keep it dual/three columned on smaller screens - because although this works on my smaller screen'd macbook (13 inch) it makes the page much much longer and requires much more scrolling. On larger screens where you can see more fields I think it's probably fine to do this.

Using bootstraps grid classes like this is a little strange...

• This isn't a bootstrap grid
• Applies flex-basis on non-flex items
• Adds horizontal padding so slightly missaligned

What is the purpose of these classes? Setting a max-width so label and field wrap?

@alikon please remove RTC due to advise from @ciar4n
@ciar4n what would you set here? mw- classes? Thank you!

Done @coolcat-creations

@coolcat-creations It depends on your intent. Are you looking to give fields a max width?...

With a max width

Without a max width

@ciar4n yes the initial issue was about the columns and that it's too hard to scan and find the setting with two columns and also about the width. I would go with max-width then

@wilsonge and @brianteeman - I see you prefer the 2 columns approach. wouldn't it be complicated then for users to find their stuff? The initial issue was about the multicolumns and I think if there is a documentation and the documentation highlights the setting you have to look for, it somehow should be at the same place if possible.

Would the solution be to have always 2 columns (1 column on mobile) and max-width set?
Are you agreeing on that?

I don't see mention of setting a max-width on fields in the issue. Regardless, as mentioned by @brianteeman best apply this globally (control-group)... https://github.com/joomla/joomla-cms/blob/4.0-dev/administrator/templates/atum/scss/blocks/_form.scss#L27

Personally I think not such a great idea. Single column forms on a fluid width UI comes with its own issues as mentioned by @wilsonge. We are fixing one problem by replacing it with another. Single column is best practice but usually used within a fixed width interface.

Shopify example...

@ciar4n
Did I understand you right: so you would make it always single column and the width of the inputs to 100% ? Just to be sure...

Honestly, I dont know what is the best solution. For me a single column form on a fluid width UI results in to much whitespace...

Personally I prefer a fixed-width UI but I don't think that is going to happen. The next alternative is 2 column similar J3.

I don't think whitespace is bad by default. I am actually fan of whitespace where it makes sense.

Can I ask for:

• Likes for 1 Column Max Width on every device
  or for
• Dislikes for 2 Columns Max width on screens above tablet
• and the "eyes" emoticon for "none of them" ?

Just to know where I should move to...
@brianteeman @ciar4n @zero-24 @wilsonge @faustonenci @ChristineWk

I don't think whitespace is bad by default. I am actually fan of whitespace where it makes sense.

True, but for me at least, this whitespace does not seem right.

I don't think whitespace is bad by default. I am actually fan of whitespace where it makes sense.

True, but for me at least, this whitespace does not seem right.

No problem, I made kind of a small voting above to know what I should change it to :-) I have no issues with 2 columns too - 3 columns might be bit hard to scan.

As compromise: I'm voting for 2 columns :-)

2 columns for me... We have more 16:9 screen

I'm all for sticking withe template design teams 3 columns

@brianteeman I am a bit confused, didn't you comment in #25891 that 3 columns are confusing for you too? Maybe I completely misunderstood the issue or the topic, can you clarify?

I personally like the 2 columns

So I just removed the 3-Columns layout now, is that fine?

I think, it's OK now :-) but not sure. Found this here:

Good finding... Thank you @ChristineWk
I have no idea how to solve that to be honest. Anyone?

maybe it helps

Thank you! But I have no idea how to solve it technically in the right way for a backend. If someone knows and can give me a hint, I'd appreciate help, otherwise I'd close the PR...

You can probably just remove the spacer from the xml.

You can probably just remove the spacer from the xml.

@ciar4n - Hm, not sure because we have also the descriptions that can cause an unwanted misalign in the colums. And the spacers are there to separate some fields logically?

For you what would be the ideal solution? The current does not offer much control where a column break should happen

I have tested this item ✅ successfully on d14bac8

I tested it on a wide screen and got the desired 2 column layout.

Maybe the expected result in the original post should be updated so new testers don't get confused.

I have tested this item ✅ successfully on d14bac8

2 column layout was displayed correctly.
Labels should be in one line to prevent layout issues

@coolcat-creations What do you think of the screenshot by @vlaucht ? Doesn't look pretty I think :)

@roland-d
no it does not... I am unfortunately not able to work on this because of my Joomla teaching activy right now :-( Anyway I am not sure if this PR should not even be closed because I think we need something like a Colum Break marker in the XML or something to define where the colums may begin first... ?

Closing. See #29706 (comment)