# \[BUG-14575\]Column Layout Problems

**URL:** <https://forum.inductiveautomation.com/t/bug-14575-column-layout-problems/26635>\
**Category:** Ignition Early Access\
**Created:** [July 17, 2019, 4:48pm UTC](https://forum.inductiveautomation.com/t/bug-14575-column-layout-problems/26635 "2019-07-17T16:48:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![connor.elison](https://avatars.discourse-cdn.com/v4/letter/c/e495f1/32.png) [@connor.elison](https://forum.inductiveautomation.com/u/connor.elison)\
**Post date:** [July 17, 2019, 4:48pm UTC](https://forum.inductiveautomation.com/t/bug-14575-column-layout-problems/26635/1 "2019-07-17T16:48:37Z")

</div>

I am using the 8.0.3 nightly and seeing strange behavior with the column layout where the most recently added component only takes up 1 column.

Steps to reproduce:

- Create a new view with a column layout
- Set small/medium/large break points to 0
- Add a component to the view and make it span 4 columns (I used a table, but appears to affect all components)
- Save and load the view in the browser, see it only spans 1 column  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/7/78a7b60adc8248c5b3a37d8e0f67c3945c7c162a.png)
- Add a second component, make that span 4 columns
- Save and load the view in the browser, see the previous component now spans 4 columns, but the new component only spans 1  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/8/834bfdc59dd05185865542f0aac99d64a624ecc8.png)
- This appears to always affect the most recently added component

---

<div class="post-metadata">

**Author:** ![mperkins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mperkins/32/71722_2.png) [@mperkins](https://forum.inductiveautomation.com/u/mperkins)\
**Post date:** [July 26, 2019, 10:41pm UTC](https://forum.inductiveautomation.com/t/bug-14575-column-layout-problems/26635/2 "2019-07-26T22:41:47Z")

</div>

Hey @connor.elison _/wave_  
I have reproduced this issue, and I have a hunch as to what it might be on our end. I logged a bug to be prioritized, and fixed.
