# Positioning bug when using motions

**URL:** <https://community.appfarm.io/t/positioning-bug-when-using-motions/1620>\
**Category:** Bug reports\
**Created:** [February 5, 2025, 1:50pm UTC](https://community.appfarm.io/t/positioning-bug-when-using-motions/1620 "2025-02-05T13:50:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![eirik.k](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/eirik.k/32/1800_2.png) [@eirik.k](https://community.appfarm.io/u/eirik.k)\
**Post date:** [February 5, 2025, 1:50pm UTC](https://community.appfarm.io/t/positioning-bug-when-using-motions/1620/1 "2025-02-05T13:50:24Z")

</div>

Had issues with stick positioning of a container when controlling visibility with a collapse motion. Seems like the collapse wrapper doesn’t respect height and or flex settings on the sticky container.

---

<div class="post-metadata">

**Author:** ![rhys](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/rhys/32/1379_2.png) [@rhys](https://community.appfarm.io/u/rhys)\
**Post date:** [February 6, 2025, 8:31am UTC](https://community.appfarm.io/t/positioning-bug-when-using-motions/1620/2 "2025-02-06T08:31:29Z")

</div>

Hi Eirik!

Could you share more screenshots relating to setup and the resulting behavior? These would be useful for us to recreate the issue internally, and to register this as a bug.

Thanks  
Rhys

---

<div class="post-metadata">

**Author:** ![eirik.k](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/eirik.k/32/1800_2.png) [@eirik.k](https://community.appfarm.io/u/eirik.k)\
**Post date:** [February 6, 2025, 3:49pm UTC](https://community.appfarm.io/t/positioning-bug-when-using-motions/1620/3 "2025-02-06T15:49:23Z")

</div>

I have replied in DM.