# Issue with Scroll Functionality After Adding Bottom Drawer

**URL:** <https://community.appfarm.io/t/issue-with-scroll-functionality-after-adding-bottom-drawer/1679>\
**Category:** Ask the community\
**Created:** [February 27, 2025, 9:01am UTC](https://community.appfarm.io/t/issue-with-scroll-functionality-after-adding-bottom-drawer/1679 "2025-02-27T09:01:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Theo](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/theo/32/1672_2.png) [@Theo](https://community.appfarm.io/u/Theo)\
**Post date:** [February 27, 2025, 9:01am UTC](https://community.appfarm.io/t/issue-with-scroll-functionality-after-adding-bottom-drawer/1679/1 "2025-02-27T09:01:00Z")

</div>

Hi!

I’m encountering an issue with the scroll functionality in my app. After adding a persistent bottom drawer, the entire application page shifts up when using the `scrollIntoView` code. This makes the app unusable, as it’s impossible to scroll back to other elements without using the inspect element tool.

Upon inspection, I found that the bottom drawer element, although invisible, exists below the page, causing this shift. This issue doesn’t occur with a temporary drawer, only with a persistent one.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/4/4e047361bdb98540089e3f5b52a5e28153b06d7e.png)

To resolve this, I assigned unique element IDs to all my scrollable containers and modified the code to scroll only within the relevant components.

**Questions:**

1. Is this behavior a bug or an expected outcome that is unavoidable with persistent drawers?
2. Does anyone have experience handling this issue effectively?

This situation complicates the creation and maintenance of generic scroll actions. I would prefer not to review every action in my app for potential scroll issues whenever I add a bottom drawer 🙂