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
{{ message }}
Repository navigation
Conflict with Gboard on Firefox for Android: selecting a suggestion appends text instead of replacing it #3990
The issue is not present after disabling uBO in the browser.
I checked the documentation to understand that the issue I am reporting is not normal behavior.
I tried to reproduce the issue when...
uBO is the only extension.
uBO uses default lists and settings.
using a new, unmodified browser profile.
Description
I’m experiencing a keyboard conflict with uBlock Origin on Firefox for Android.
A specific URL where the issue occurs.
No
Steps to Reproduce
Enable uBlock Origin on Firefox for Android.
Open any text input field (e.g., search bar, form field).
Type a partial word, for example "ca".
Gboard shows a suggestion, e.g., "Cagliari".
Tap the suggestion to accept it.
Expected behavior
The suggestion should replace the typed text (so "ca" becomes "Cagliari").
Troubleshooting information
· The issue does not occur in Firefox private/incognito mode (where extensions are disabled by default).
· Disabling uBlock Origin completely resolves the problem.
· The issue seems specific to the combination of uBlock Origin + Gboard + Firefox for Android. It does not happen with other keyboards (tested with SwiftKey) or with other browsers.
Environment:
· Device: Oppo A40m
· OS: ColorOS 15 (Android 15)
· Browser: Firefox for Android (latest version)
· Keyboard: Gboard (latest version)
· Extension: uBlock Origin (latest version)
Workaround found:
Replace uBlock Origin with an alternative blocker (e.g., AdGuard) or disable uBlock Origin entirely. The problem disappears as soon as uBlock Origin is turned off.
It's probably a regression in the Firefox 150 code for Android. Hunt for patch 150.0.1, for me it reduced the errors with hints (there was no Gboard update for my device at that time).
I assume the search box is on websites and not in the Firefox interface (there are probably only a few pre-MV2 add-ons that can barely reach there, if you were to use 56 release on purpose/deliberately/consciously).
Activity
krystian3w commentedon Apr 29, 2026
It's probably a regression in the Firefox 150 code for Android. Hunt for patch 150.0.1, for me it reduced the errors with hints (there was no Gboard update for my device at that time).
I assume the search box is on websites and not in the Firefox interface (there are probably only a few pre-MV2 add-ons that can barely reach there, if you were to use 56 release on purpose/deliberately/consciously).