The whole URL is replaced and typing starts from beginning of URL
Sometimes URL is rendered from the middle and Firefox is proposing some other URL on the end. It looks for me, that it happens the most often when typing is done fast after step 2 (around 1s or less) - probably something is not refreshed fast enough or some event is not sent on time and user is faster.
Note: URLs are only examples, it happens for other combinations too.
I haven't been able to reproduce this @marcinwiacek. Could you provide screenshots, a video, or more detail?
@boek You mentioned you had a video or STR here? Could you post?
We can't seem to reproduce this, which means it may be fixed. I'd love QA on this.
I have managed to reproduce this issue on Beta 4.0.0-beta.1 (Build #20500409) 2/19 on a Samsung Galaxy S8+ (Android 8.0.0) by performing the following steps:
The whole URL is replaced and typing starts from beginning of URL
The website from step 1 is kept in the address bar. Please see the attached video for further information.

On my Pixel 4, repeating these steps, the entire URL is replaced with the search term.
@LaurentiuApahideanSV It might be related to the keyboard you are using. Could you specify if you are using Swiftkey or some other custom keyboard? I am working on a similar issue https://github.com/mozilla-mobile/fenix/issues/6290
@codrut-topliceanu The keyboard I used to reproduce the issue is the default Samsung Keyboard.
@LaurentiuApahideanSV Confirmed (Samsung Galaxy Note 10, Android 10). It's related to the newer Samsung Keyboard. The bug & behaviour is completely different on swiftkey. On Gboard it works as it should.
The root of all of this is the InlineAutocompleteEditText android component, which handles the suggestions displayed in the URL editText from the SearchFragment. I did propose a fix in #6290 for Swiftkey, but I don't think it's the right one. We can't fix this on a keyboard by keyboard basis.
I'll continue working on it so that maybe I can find a single fix that would solve the problems for all keyboards. Though I could really use some input from @csadilek and maybe @mcomella, as they have worked on this component before.
Looks like @codrut-topliceanu is already working on this. :)
@jonalmeida offering me as tribute :)))
This should be fixed by https://github.com/mozilla-mobile/android-components/issues/6751
I am unable to reproduce it anymore.
I could use confirmation on that though.
Whoops! I didn't realize that comment we 3 months ago! 😅
Hi, I can confirm that the issue is fixed using the latest version of Firefox Preview Nightly 5/6 #21270609.
Devices:
Most helpful comment
@jonalmeida offering me as tribute :)))
This should be fixed by https://github.com/mozilla-mobile/android-components/issues/6751
I am unable to reproduce it anymore.
I could use confirmation on that though.