I was just trying to autofill an alias, I typed "@ama" pressed right, the space is not automatically inserted anymore, so I can't continue typing.

Is the update2 pref on? I intentionally removed the space since pressing space or enter with a typed/autofilled token alias should enter search mode now.

yes, it's on, the problem is that autofilling with RIGHT is a common thing in our autocomplete.

Set release status flags based on info from the regressing bug 1647890

Yes, but the trailing space is an indicator that the user should just start typing. With search mode enabled, we'd like the user to hit space or enter to enter search mode first.

We can certainly revert to the old behaviour, but my understanding is that search mode is supposed to replace alias use altogether; aliases will just become a way to enter search mode. Maybe we could enter search mode when autofill is confirmed with right?

I'll mark this blocked-ux and discuss with Verdi.

(In reply to Harry Twyford [:harry] from comment #4)

We can certainly revert to the old behaviour, but my understanding is that search mode is supposed to replace alias use altogether; aliases will just become a way to enter search mode. Maybe we could enter search mode when autofill is confirmed with right?

I think I didn't explain well, I'm typing "@ama", I get suggested "@ama[zon]" I press RIGHT to confirm the "zon" completion, at this point search mode should be enabled, I should be able to continue typing, without having to further type another space.
Not entering search mode means that I get "@amazonmysearch" that is definitely not expected, I end up searching the whole string on Google.
If I press Enter instead of Right, it works as expected.

Oh, I see! Yes, I agree. Are you alright if we close this bug and handle this as part of bug 1657676? I could add a comment saying we should support the behaviour you describe.

bug 1657676 seems to be more about their visualization and a view bug, this is an input field bug.

Fair enough!

Hi Harry, are you expecting to get to this any time soon? Thanks!

This bug only affects users with the browser.urlbar.update2 pref enabled. That pref is currently Nightly-only. Its wider release was originally slated for 81, but it's since been pushed back to 82, so Beta 81 and Release 81 users will not experience this. I'm not sure how that should be reflected in release tracking.

I can probably look into this in the next days.

https://hg.mozilla.org/mozilla-central/rev/0d3406e53a85

The patch landed in nightly and beta is affected.
:mak, is this bug important enough to require an uplift?
If not please set status_beta to wontfix.

For more information, please visit auto_nag documentation.

no need for this fix in beta.

I verified this issue using 82.0a1 (2020-09-14) on macOS 10.13 and Windows 10 x64.
Adrian could you help me with Ubuntu verification?

Verified as fixed using latest Nightly 82.0a1 2020-09-17 under Ubuntu 18.04 64-bit.