1928353 - Extra space between the toolbar and keyboard

Status: RESOLVED WORKSFORME

(Firefox for Android :: Toolbar, defect, P3)

Description

[Artyom [:Arutemu64]]

Attachment: Screenshot_20241031_141635_org.mozilla.firefox_beta.jpg

User Agent: Mozilla/5.0 (Android 10; Mobile; rv:133.0) Gecko/133.0 Firefox/133.0

Steps to reproduce:

Press on text input field, in some cases there is blank space between toolbar and keyboard (I use Microsoft SwiftKey if that helps)

Actual results:

Blank space between toolbar and keyboard

Expected results:

There should be no space between toolbar and keyboard

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Fenix::Toolbar' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Chris Peterson [:cpeterson]]

Artyom, thanks for reporting this issue and sharing the screenshot.

Can you reproduce this issue if you switch from Microsoft SwiftKey to the default Android keyboard?

Do you know if this is a recent bug or something you've seen for a long time? Can you reproduce this bug in Firefox 132 (the non-Beta release version of Firefox)?

Comment 3

[Artyom [:Arutemu64]]

Attachment: 132.0_swiftkey.jpg

Comment 4

[Artyom [:Arutemu64]]

Attachment: 133.0b6_swiftkey.jpg

Comment 5

[Artyom [:Arutemu64]]

Attachment: 133.0b6_gboard.jpg

Comment 6

[Artyom [:Arutemu64]]

(In reply to Chris Peterson [:cpeterson] from comment #2)

Can you reproduce this issue if you switch from Microsoft SwiftKey to the default Android keyboard?

It seems like Firefox toolbar doesn't play nice with SwiftKey ever since 133 release, I tried switching to Gboard and it looks okay (although the animation is still kinda laggy). I attached few screenshots for comparison.

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.

Comment 8

[Chris Peterson [:cpeterson]]

Thanks for sharing the screenshots. This looks like a regression in Fx 133 that affects SwiftKey. An engineer will try to reproduce on their device.

In the meantime, can you please try testing our new toolbar design? To enable it:

1. You will need to test using Firefox Nightly: https://play.google.com/store/apps/details?id=org.mozilla.fenix
2. Enable debug mode: open the Settings menu, scroll to the bottom, and select "About Firefox Nightly", and tap on the Firefox logo five times.
3. Open the Settings menu again, scroll to the bottom, and select "Secret Settings".
4. Enable the "Enable Navigation Toolbar" setting and return to the web page.

Comment 9

[Artyom [:Arutemu64]]

Attachment: 134.0a1 (Build #2016055815)_swiftkey.jpg

New toolbar design is also affected

Comment 10

[Artyom [:Arutemu64]]

Attachment: 133.0b7_gboard.jpg

Just realized that this bug is still present with Gboard.

For more context, I'm using Honor View 20 with Magic UI 5.2.0 (based on Android 10).

Comment 11

[Donal Meehan [:dmeehan]]

:cpeterson any updates on the investigation mentioned in Comment 8?
(133.0 is in now in RC)

Comment 12

[Chris Peterson [:cpeterson]]

New toolbar design is also affected
Just realized that this bug is still present with Gboard.

Thanks for testing these different settings! This is very helpful.

:cpeterson any updates on the investigation mentioned in Comment 8?

I will follow up with the engineers.

Comment 13

[Petru-Mugurel Lingurar [:petru]]

In the above screenshots I see the system's status bar but I don't see the system's navigation bar.
Is the navigation bar hidden in any way?
Does the issue still reproduces if using 3 buttons navigation?

Comment 14

[Artyom [:Arutemu64]]

Attachment: 133.0b9_swiftkey_navbar.jpg

I primarily use gesture navigation. I enabled navigation bar, but there is still extra space between the keyboard and toolbar in some cases, although it's now thinner.

Worth mentioning, it doesn't happen every time I focus on a text field, but like once in 10 tries.

Comment 15

[Petru-Mugurel Lingurar [:petru]]

@ QA Can you help checking this on more devices with Android 10 and 11+ while ensuring to also test on Huawei devices?
I can't reproduce with emulators and seems like a (Huawei) framework issue so I'm curious if things improved on newer versions of Android.

Comment 16

[Delia Pop (Android QA)]

Attachment: huawei p40 Lite_A10.mp4

We were able to reproduce this issue, but only with a single device, Huawei p40 Lite (Android 10) and with the SwiftKey keyboard. Couldn't reproduce with the Gboard and Celia keyboards.
The repro rate was ~ 6/10 tries on Nightly 134.0a1 from 11/21.

Not reproducible with other devices. We've tried with:

• Xiaomi Mi8 Lite (Android 10)
• Samsung Galaxy Note 8 (Android 9)
• Samsung Galaxy S22 Ultra (Android 14)
• Motorola Moto G30 (Android 12)
• OPPO A15s (Android 10)
• Xiaomi Redmi Note 8T (Android 11)

Comment 17

[Donal Meehan [:dmeehan]]

Setting Fx133 to fix-optional based on Comment 16.
We could still take a fix if we had one in time for a dot release.

Comment 18

[Petru-Mugurel Lingurar [:petru]]

Hi @Artyom, wanted to double check - can you confirm you reproduce this issue in a Huawei device with Android 10?
This seems to be the only device family affected.

Comment 19

[Artyom [:Arutemu64]]

(In reply to Petru-Mugurel Lingurar [:petru] from comment #18)

Hi @Artyom, wanted to double check - can you confirm you reproduce this issue in a Huawei device with Android 10?
This seems to be the only device family affected.

Yes, I'm using Honor View 20 (it was released before splitting from Huawei so it's basically a Huawei device) running Magic UI 5.2.0 (also known as EMUI 12) based on Android 10.

Comment 20

[Petru-Mugurel Lingurar [:petru]]

With the patch for bug 1933488 landed I think this issue also disappeared in the latest Nightly.
@Delia / @Artyom can you please verify and confirm?

Comment 21

[Delia Pop (Android QA)]

This issue is no longer reproducible on our side in the latest Nightly 135.0a1 from 12/10 with Huawei p40 Lite (Android 10) and with the SwiftKey keyboard.
I'll wait for Artyom's confirmation and then update the ticket accordingly.

Comment 22

[Artyom [:Arutemu64]]

I can't reproduce the issue with Nightly 2016061378 anymore so I would consider this as fixed 👍