# Issues with 'absolute' Positioning

**URL:** <https://community.thunkable.com/t/issues-with-absolute-positioning/21715>\
**Category:** Questions about Thunkable X\
**Created:** [April 9, 2018, 6:01pm UTC](https://community.thunkable.com/t/issues-with-absolute-positioning/21715 "2018-04-09T18:01:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amelie\_Garcia](https://avatars.discourse-cdn.com/v4/letter/a/bbe5ce/32.png) [@Amelie\_Garcia](https://community.thunkable.com/u/Amelie_Garcia)\
**Post date:** [April 9, 2018, 6:01pm UTC](https://community.thunkable.com/t/issues-with-absolute-positioning/21715/1 "2018-04-09T18:01:23Z")

</div>

Hi,  
I am new to Thunkable and noticed that you can change a component’s positioning from the default ‘relative’ to ‘absolute’. I did this and saw how other components’ margins would now no longer change the position of the first component.

I also noticed that you could still add margins to the component with ‘absolute’ positioning and change its position in that way, but when I did a ‘Live Test’ with my phone the component was positioned in the **center** of the row I had placed it in, and not to the **side**. Which is where it was shown to be positioned on the preview due to my changing the component’s margins.

Thought you should know,  
Amelie

---

<div class="post-metadata">

**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, 12:04pm UTC](https://community.thunkable.com/t/issues-with-absolute-positioning/21715/2 "2024-11-08T12:04:06Z")

</div>