# Column Container pushing components erratically

**URL:** <https://forum.inductiveautomation.com/t/column-container-pushing-components-erratically/67985>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [December 26, 2022, 8:02pm UTC](https://forum.inductiveautomation.com/t/column-container-pushing-components-erratically/67985 "2022-12-26T20:02:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![smcfarlane](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/smcfarlane/32/42150_2.png) [@smcfarlane](https://forum.inductiveautomation.com/u/smcfarlane)\
**Post date:** [December 26, 2022, 8:02pm UTC](https://forum.inductiveautomation.com/t/column-container-pushing-components-erratically/67985/1 "2022-12-26T20:02:21Z")

</div>

Ignition version 8.0.14

Using a column container to set up a grid of buttons and when trying to add buttons to a row, the rest of the components will get pushed seemingly at random.

Before adding the button

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/7/c759b24d14950037cbd1c08cd2e23cf16ba47e57.png)

Adding a button to the next row causes absolute chaos.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/0/7024a7e09c0445de12d23a0eeb9c97a54087ba5e.png)

Why would adding a button to row 5 push objects in other rows? Is this a bug? Or am I doing something to cause this behavior. Notice how D4 and D5 have swapped in addition to D6 being pushed to a new 'sub row'

Adding a button from the component picker or doing a copy and paste does the same thing.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [December 27, 2022, 3:40am UTC](https://forum.inductiveautomation.com/t/column-container-pushing-components-erratically/67985/2 "2022-12-27T03:40:06Z")

</div>

I stopped using the column container with this being one of the main reasons. The others being that it's so much work to configure all of the sizes, and if you want to add new components, it's an utter nightmare. I would recommend a flex container with wrapping

---

<div class="post-metadata">

**Author:** ![smcfarlane](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/smcfarlane/32/42150_2.png) [@smcfarlane](https://forum.inductiveautomation.com/u/smcfarlane)\
**Post date:** [December 27, 2022, 2:09pm UTC](https://forum.inductiveautomation.com/t/column-container-pushing-components-erratically/67985/3 "2022-12-27T14:09:12Z")

</div>

Is this a known issue then?

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [December 27, 2022, 8:02pm UTC](https://forum.inductiveautomation.com/t/column-container-pushing-components-erratically/67985/4 "2022-12-27T20:02:04Z")

</div>

Yours might be, but my reasons are more due to implementation than due to issues

---

<div class="post-metadata">

**Author:** ![smcfarlane](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/smcfarlane/32/42150_2.png) [@smcfarlane](https://forum.inductiveautomation.com/u/smcfarlane)\
**Post date:** [December 28, 2022, 8:44pm UTC](https://forum.inductiveautomation.com/t/column-container-pushing-components-erratically/67985/5 "2022-12-28T20:44:08Z")

</div>

Seems to be a very temperamental container. I tried doing the same thing in 2 other versions. 8.1.21 and 8.1.22 (pulled from @Kevin.Collins latest on dockerhub) and got some...interesting results. 8.1.21 appears to work as intended  
 ![Working_column_container](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/3/636207a87370ac25c248849de0be162cfd95b90d.gif)

8.1.22 is broken, but in a different way.  
 ![Broken_column_container](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/a/ea38bcf678796d2bb4257ffd1549020e6e456dfa.gif)

I think you're right, best to just avoid using the column container for now.