1656152 - Address bar autocompletes "wnc" to "www.google.com" when it's typed too fast

Status: RESOLVED DUPLICATE of bug 1653436

(Firefox :: Address Bar, defect, P2)

Description

[Dustin L. Howett]

Attachment: addressbar_eating_input.gif

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0

Steps to reproduce:

This is likely specific to my sites, bookmarks and browsing history, so it is likely going to be difficult to reproduce. I was testing the cases from #1655363, and while I can confirm that www doesn't erroneously autocomplete to woogle.com, I'm still seeing the partial match replaced with an incorrect completion.

Open a new tab, quickly enter wnc or wat.

Actual results:

I end up with w.google.com or wamtea.slack.com in the address bar.

It seems like a search is dispatched after the first character and when it comes back it destroys the second and third characters.

Comment 1

[Dustin L. Howett]

In the first instance, wnc, it still highlights www as the matching portion of the URL once it has deleted the nc.

If I type more slowly, w n c, the result usually comes back after the n, result in w.google.com which is then overstruck with c.

Comment 2

[Marco Bonardo [:mak]]

Can you help us findind a regression range using mozregression? I think you can copy your profile to a new one and ask mozregression to use that new testing profile.
Im wondering if this is related to bug 1653436, rather than being leftover from bug 1655363.

Comment 3

[Marco Bonardo [:mak]]

I assume even if you confirm it, the final navigation is correct?

Comment 4

[Marco Bonardo [:mak]]

I can sort-of reproduce something like this typing "wc" and having it complete to "ww.google.com". I'll see if I can figure out something.

Comment 5

[Marco Bonardo [:mak]]

We could wrap this in an if, but I feel like we should not print an handled exception message to the console in general. Just try this in the Browser Console:
try{Services.uriFixup.getFixupURIInfo("", 0)} catch (ex) {}
on the contrary this works:
try{throw new Components.Exception("test", Cr.NS_ERROR_FAILURE);} catch (ex) {}

Nathan, do you have any idea about this, or do you know someone who could chime in?

Comment 6

[Marco Bonardo [:mak]]

oops wrong bug

Comment 7

[Marco Bonardo [:mak]]

I'm duping to bug 1653436, the underlying issue is the same. If the patches there should not resolve it once landed, we can re-evaluate.