# Expanding group moves all child elements \[Nov 2022\] **URL:** \ **Category:** Issues / Bugs\ **Created:** [November 20, 2022, 11:48am UTC](https://community.thunkable.com/t/expanding-group-moves-all-child-elements-nov-2022/2139877 "2022-11-20T11:48:12Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![jared](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jared/32/138473_2.png) [@jared](https://community.thunkable.com/u/jared)\ **Post date:** [November 20, 2022, 11:48am UTC](https://community.thunkable.com/t/expanding-group-moves-all-child-elements-nov-2022/2139877/1 "2022-11-20T11:48:12Z")
Today when expanding a group’s width, all child elements were moving vertically out of the group. This is no good and terrible for UI/UX. Start watching at second marker :18 https://player.vimeo.com/video/772984583?h=3a3df07ac6&app_id=122963 ---
**Author:** ![matt\_conroy](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/matt_conroy/32/150843_2.png) [@matt\_conroy](https://community.thunkable.com/u/matt_conroy)\ **Post date:** [November 21, 2022, 4:04pm UTC](https://community.thunkable.com/t/expanding-group-moves-all-child-elements-nov-2022/2139877/2 "2022-11-21T16:04:41Z")
Thanks for flagging this, @jared. Not a great situation at all, I’m sorry that is happening. I’m having trouble recreating the issue in an [MVP](https://x.thunkable.com/copy/6d881d624f965e8f93bbf60a72421b41), however. Are you seeing this outside of that particular project as well? ---
**Author:** ![jared](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jared/32/138473_2.png) [@jared](https://community.thunkable.com/u/jared)\ **Post date:** [November 21, 2022, 4:15pm UTC](https://community.thunkable.com/t/expanding-group-moves-all-child-elements-nov-2022/2139877/3 "2022-11-21T16:15:49Z")
I only see this in projects with a bunch of groups on a screen. Not sure of the particular number of screens required to make it happen. it only happens on more complex screens. probably an edge case but there’s not that much on that screen. I’ll be sure that I’m on the latest chrome version and do a hard refresh too ---
**Author:** ![matt\_conroy](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/matt_conroy/32/150843_2.png) [@matt\_conroy](https://community.thunkable.com/u/matt_conroy)\ **Post date:** [November 21, 2022, 4:21pm UTC](https://community.thunkable.com/t/expanding-group-moves-all-child-elements-nov-2022/2139877/4 "2022-11-21T16:21:17Z")
Got ya–I’ll keep messing with my MVP so see if/when it happens. ---
**Author:** ![muneer](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/muneer/32/75210_2.png) [@muneer](https://community.thunkable.com/u/muneer)\ **Post date:** [November 22, 2022, 11:10am UTC](https://community.thunkable.com/t/expanding-group-moves-all-child-elements-nov-2022/2139877/5 "2022-11-22T11:10:43Z")
I have noticed that once you reposition the component using the X and Y coordinates instead of dragging, it starts to behave as **not part of the group**. What was more confusing that it is not happening all the time. ---
**Author:** ![jared](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jared/32/138473_2.png) [@jared](https://community.thunkable.com/u/jared)\ **Post date:** [November 22, 2022, 11:38am UTC](https://community.thunkable.com/t/expanding-group-moves-all-child-elements-nov-2022/2139877/6 "2022-11-22T11:38:58Z")
> [@muneer](#): > > What was more confusing that it is not happening all the time. Same. It happens only at the inconvenient times. 🤣 ---
**Author:** ![matt\_conroy](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/matt_conroy/32/150843_2.png) [@matt\_conroy](https://community.thunkable.com/u/matt_conroy)\ **Post date:** [November 22, 2022, 2:23pm UTC](https://community.thunkable.com/t/expanding-group-moves-all-child-elements-nov-2022/2139877/7 "2022-11-22T14:23:18Z")
Thanks for flagging this part as well, @muneer. Layout positioning has always frustrated me a bit with Thunkable. These were literally taken from a project I am currently working on: x=44.765625 and y=173.35937499999997. I’m sure lots of users would just round those to 45 and 174. ---
**Author:** ![jared](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jared/32/138473_2.png) [@jared](https://community.thunkable.com/u/jared)\ **Post date:** [November 22, 2022, 3:38pm UTC](https://community.thunkable.com/t/expanding-group-moves-all-child-elements-nov-2022/2139877/8 "2022-11-22T15:38:16Z")
Rounding to the nearest pixel would be lovely, imho ---
**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\ **Post date:** [November 8, 2024, 1:12pm UTC](https://community.thunkable.com/t/expanding-group-moves-all-child-elements-nov-2022/2139877/9 "2024-11-08T13:12:44Z")