x.com - The keyboard overlaps the password field when attempting to log in
Categories
(Web Compatibility :: Site Reports, defect, P3)
Tracking
(firefox129 affected, firefox130 affected)
People
(Reporter: rbucata, Unassigned, NeedInfo)
References
(Depends on 1 open bug, )
Details
(Keywords: webcompat:platform-bug, webcompat:site-report)
User Story
platform:android impact:annoyance-minor configuration:general affects:all branch:release diagnosis-team:layout
Attachments
(1 file)
278.89 KB,
image/png
|
Details |
Environment:
Operating system: Android 12/ Android 13
Firefox version: Firefox Nightly 130.0a1 (2016036335-🦎130.0a1-20240803095257🦎)
Preconditions:
Clean profile
Steps to reproduce:
- Navigate to: https://x.com/i/flow/login
- Introduce the required email and proceed
- When prompted, tap inside the password field and observe
Expected Behavior:
The password field is not overlaped
Actual Behavior:
The keyboard overlaps the password field
Notes:
- Reproducible regardless of the status of ETP
- Reproducible on the latest build of Firefox Nightly and Release
- Works as expected using Chrome
- Attachment provided
- Issue found during WebCompat team [Top100] websites testing
Reporter | ||
Updated•1 month ago
|
Reporter | ||
Updated•1 month ago
|
Updated•1 month ago
|
Comment 1•10 days ago
|
||
I can't reproduce in current Nightly.
I do see that the viewport-size behavior differs in Nightly vs. Release -- I'm not getting the field covered up in release, but it is in a more-constrained viewport and I can imagine that with a smaller screen it might end up covered up. (I'm using a Pixel 8 FWIW) I think that release vs. Nightly change would be from bug 1884807.
So I'm guessing bug 1884807 will have fixed this (along with similar bugs like bug 1884131) -- Raul, would you mind retesting to see if you can still repro?
Comment 2•4 days ago
•
|
||
I'm assuming my hunch at the end of comment 1 is correct, in which case we can consider this diagnosed as depending on bug 1884807 (and hence fixed-in-nightly), and also depending on bug 1916002, which blocks this from being closed since this will continue affecting release users until we take action there.
Description
•