# Display bug on scroll how to deal with?

**URL:** <https://community.weweb.io/t/display-bug-on-scroll-how-to-deal-with/8586>\
**Category:** Ask us anything\
**Created:** [May 14, 2024, 6:57am UTC](https://community.weweb.io/t/display-bug-on-scroll-how-to-deal-with/8586 "2024-05-14T06:57:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Davy](https://avatars.discourse-cdn.com/v4/letter/d/e495f1/32.png) [@Davy](https://community.weweb.io/u/Davy)\
**Post date:** [May 14, 2024, 6:57am UTC](https://community.weweb.io/t/display-bug-on-scroll-how-to-deal-with/8586/1 "2024-05-14T06:57:45Z")

</div>

Hi guys,

I was curious to know, how do you guys deal with this type of bug once published?

> **[Screen\_Recording\_20240514-073659\_Chrome.mp4](https://drive.google.com/file/d/1SSO6_2ahbB4wCPgMgGEQlTQSZpmC-SU_/view?usp=drive_link)**
>
> Google Drive file.

I have a sticky CTA, but seems like it’s not as sticky when I scroll “fast” on my phone.

Any idea?

Here are the settings:

 ![Screenshot 2024-05-14 at 08.56.52](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/f/fd6adf20e63df68b2a61c466156f03942fb5ec1a.png)  
 ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/d/d81921ffe300f91d984b10ff398fe7435c9071cd.png)

---

<div class="post-metadata">

**Author:** ![jptrinh](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/jptrinh/32/1493_2.png) [@jptrinh](https://community.weweb.io/u/jptrinh)\
**Post date:** [May 14, 2024, 8:38am UTC](https://community.weweb.io/t/display-bug-on-scroll-how-to-deal-with/8586/2 "2024-05-14T08:38:01Z")

</div>

Humm does it behave the same if you put a fixed position (I think this value should also work for your use-case?) instead of a sticky?

---

<div class="post-metadata">

**Author:** ![Davy](https://avatars.discourse-cdn.com/v4/letter/d/e495f1/32.png) [@Davy](https://community.weweb.io/u/Davy)\
**Post date:** [May 14, 2024, 8:50am UTC](https://community.weweb.io/t/display-bug-on-scroll-how-to-deal-with/8586/3 "2024-05-14T08:50:59Z")

</div>

My concern with fixed positioning is that the rendering differs on mobile devices between iOS and Android. What would you recommend?

---

<div class="post-metadata">

**Author:** ![Alexis](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/alexis/32/13248_2.png) [@Alexis](https://community.weweb.io/u/Alexis)\
**Post date:** [May 21, 2024, 2:36pm UTC](https://community.weweb.io/t/display-bug-on-scroll-how-to-deal-with/8586/4 "2024-05-21T14:36:53Z")

</div>

Hi, it’s seems to be a known browser related bug [Mobile browser bars being hidden can affect CSS position sticky bottom | Steve Fenton](https://www.stevefenton.co.uk/blog/2022/12/mobile-position-sticky-issue/)

The simplest solution suggested is

> If you add any fixed-position element to the page, the bug with the sticky position element just goes away. The fixed-position element somehow triggers some form of tracking that probably ought to be triggered by sticky-positioned elements, too - so just by adding an empty element with `position: fixed` the problem is solved.

You may try this one. Add an empty element with a fixed position or add the fixed position to one of your element in the page if you can.

---

<div class="post-metadata">

**Author:** ![Davy](https://avatars.discourse-cdn.com/v4/letter/d/e495f1/32.png) [@Davy](https://community.weweb.io/u/Davy)\
**Post date:** [May 21, 2024, 3:10pm UTC](https://community.weweb.io/t/display-bug-on-scroll-how-to-deal-with/8586/5 "2024-05-21T15:10:50Z")

</div>

Thank you @Alexis will do it.

---

<div class="post-metadata">

**Author:** ![Davy](https://avatars.discourse-cdn.com/v4/letter/d/e495f1/32.png) [@Davy](https://community.weweb.io/u/Davy)\
**Post date:** [May 28, 2024, 7:31am UTC](https://community.weweb.io/t/display-bug-on-scroll-how-to-deal-with/8586/6 "2024-05-28T07:31:21Z")

</div>

I have tried, but the issue persists. It didn’t fix it