Gutenberg: Column Block - Reducing the number of columns deletes content

[amjadr360]

Describe the bug
Whenever I change 3 columns into 2 the 3rd one gets eliminated along with its content. Instead 3rd column content should shift into next row. I can get my 3rd column's content by doing undo but it is not a good approach and even I do undo Columns option sate stay on 2 and when I hit update 3rd column content get deleted.

Screenshots
Here screen record.
https://drive.google.com/file/d/1gAxuRi7FPFMKWwoDtMYlkpQxXP2F1Gjm/view?usp=sharing

To Reproduce
Steps to reproduce the behavior:

1. Go to 'edit post'
2. Add three columns and add content inside all of them.
3. Then change 3 columns to 2 columns
4. You will see 3rd columns will eliminate along with its content.

Expected behavior
Instead got eliminated 3rd column content should shift into next row.

Desktop (please complete the following information):

• OS: [Windows]
• Browser [Chrome, safari]

Additional context
Wordpress Version 4.9.8
Gutenberg Version 3.5.0

[GhostPirateBob]

Congratulations on open issue 1000! 🎉🎉🎉🎉

[eddhurst]

Quick note to say that I can replicate this, see gif.

Replicated on:

Desktop:
OS: Mac Sierra 10.12.6
Browser: Chrome
Version: 69.0.3497.100

Additional context
Gutenberg 3.9

[bfintal]

An issue I see is if the expected behavior is to merge the disappearing column's contents with the last content is that all the content would pile up and make the UI a mess. Then ideally, if all the disappearing content gets piled up in the 2nd column, changing it back to 3 columns should also undo the piling up. This might complicate things.

I would like to suggest an alternative behavior: just make the disappearing column's content hidden but still there. In the scenario, when the column count is set from 3 to 2, the content of the 3rd column would just be hidden. Then when the column is brought back to 3, it would just be present again. It would be up to the user to move things around.

[youknowriad]

I think this needs to be improved design-wise. Ideally removing a column is an explicit action (clicking a "x" or something like that) instead of a range input.

[leecollings]

Can I also add to this that the range input should be removed, as if it is set to 2, and I have content in both my columns, I can click on this input, and delete the value and then proceed to type a different number (3 for example).

The result I am left with, because I deleted the value of 2, is that ALL of my column content is deleted and lost.

[strarsis]

I have a similar issue: Example: There are 4 columns. The 3rd column may be completely empty.
'When now reducing the column count of the columns block,
the 4th column should become the 3rd column.
Instead, currently the 4th column is simply removed while retaining the 3rd empty column.

Additionally, a method for swapping or reordering the columns would be a nice addition.

[draganescu]

in support of @leecollings:

Describe the bug

When we alter the number of columns using the input instead of the slider the content is not saved.

To reproduce

Steps to reproduce the behavior:

• In a post or page
• Add a column block
• Write some text in both blocks
  -Select the columns block
• Modify the number of columns in the inspector by changing the number in the input, instead of the slider, e.g. instead of 2, delete 2 and write 3
• Content is gone.

Expected behavior

To behave like the slider:

• If I am adding columns the content remains
• If I am removing the content is deleted RTL
• If I add the same number the content is saved

[melchoyce]

I think part of the problem here is I expect the columns to act like a grid — if I have three columns of content and reduce that number to two, I expect that third column to drop down into a new row beneath the top-left column. If I then set my columns back up to three, I expect that dropped column to flow back up into the original row:

Edit: Maybe we just need a grid block?

[msdesign21]

Grid block sounds interesting!