[SwipeableDrawer] Can't scroll drawer content if anchor="bottom" and Virtual Keyboard is open

[Aleksan4e3]

Steps to reproduce

Steps:

1. Open this link to live example: (https://7ppfwt.csb.app/)
2. Click on 'Bottom'
3. Click on Input field
4. When Virtual Keyboard will be open, try to scroll

Current behavior

I can't scroll to the end.

Expected behavior

I can scroll to the end

Context

No response

Your environment

IOS 18.3.2
Browser - Chrome 134

Search keywords: SwipeableDrawer

[DiegoAndai]

Hey @Aleksan4e3, thanks for the report. I'm still able to scroll with the keyboard

All.Photos.-.1.of.1.mov

Is your issue that you're not able to reach the end? Have you tried adding padding when the input is selected?

[Aleksan4e3]

Hey @Aleksan4e3, thanks for the report. I'm still able to scroll with the keyboard

All.Photos.-.1.of.1.mov
Is your issue that you're not able to reach the end? Have you tried adding padding when the input is selected?

Hello @DiegoAndai, thanks for the quick reply. Yes, my issue that I am not able to reach the end.
I adjusted example to add padding bottom if keyboard is open. Also I added some input fields to the middle and to the end.

video_2025-04-01_20-52-57.mp4

Now if I click on First input all works as expected. But there are some others cases:
1-st:

1. Click 'Bottom'
2. Click on 'TextStart' input.
3. Click on 'TextEnd' input.
   Result - I see empty space in the bottom
   Expected - no empty space in the bottom

2-nd

1. Click 'Bottom'
2. Click on 'TextEnd' input.
3. Try to scroll to the start
   Result - I am not able to reach start
   Expected - I can reach start

PS. I think the reason is different 'viewport resize behavior' link. I added 'interactive-widget=resizes-content' meta tag in index.html to fix behaviour on Android. But it's not supported for IOS

[DiegoAndai]

I think this is an external dependency issue, and it will have to be handled differently depending on different browsers or OS.

I added the waiting for 👍🏼 label so the community can vote for this fix. If you want to see this implemented, please add a 👍🏼 reaction to the issue's description.

Sorry I can't be of any more help at this moment, I'm not familiar enough with Android/iOS differences to come up with a workaround. If someone has one, sharing it would be greatly appreciated.