You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
opening and closing the search's (strg+f) keyboard shouldn't move the viewport
Current Behavior
I open the search, the keyboards gets opened and the viewport moves upward. This does not happen on Chrome on Android. It also doesn't happen on other web pages on Firefox on Android.
Why is this an issue? because if you click anything while the keyboard is opened then Firefox will click on the page but close the keyboard first. The touch ends up on a different position of the viewport than intended, which can be quite annoying:
Does anyone have an idea why the viewport moves at all? it moves upwards with the keyboard. Is this a css setting?
I'm not sure, yet, whether this is a bug in Firefox or this page. I haven't found any other page, yet, where the view port moves like this
The text was updated successfully, but these errors were encountered:
Your Environment
Firefox on Android (Android 14, Pixel 7 Pro)
Expected Behavior
opening and closing the search's (strg+f) keyboard shouldn't move the viewport
Current Behavior
I open the search, the keyboards gets opened and the viewport moves upward. This does not happen on Chrome on Android. It also doesn't happen on other web pages on Firefox on Android.
Why is this an issue? because if you click anything while the keyboard is opened then Firefox will click on the page but close the keyboard first. The touch ends up on a different position of the viewport than intended, which can be quite annoying:
Steps to Reproduce
https://youtu.be/5FwTLYSi0C0?si=ztS7p6prMag7pM7R
Does anyone have an idea why the viewport moves at all? it moves upwards with the keyboard. Is this a css setting?
I'm not sure, yet, whether this is a bug in Firefox or this page. I haven't found any other page, yet, where the view port moves like this
The text was updated successfully, but these errors were encountered: