Closed Bug 1509487 Opened 6 years ago Closed 4 years ago

When I drag&drop text to address bar it's giving other result than entering text and pressing enter

Categories

(Firefox :: Address Bar, defect, P3)

63 Branch
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mv, Unassigned)

Details

(Whiteboard: [fxsearch])

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

Steps to reproduce:

When I enter abc/def to address bar and press enter, it's searching on google - which is the way I need. If I drag&drop the same text to the address bar it's going to abc.de/def which is completely wrong


Actual results:

Firefox is looking for domain instead of searching


Expected results:

the same as pressing enter on address bar -> searching on google.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0
20181123100103

I end up on https://abc.go.com/def instead, which is due to the en-US locale. So the issue is reproducible, though I don't know what the intended behavior is.
Has STR: --- → yes
Component: Untriaged → Address Bar
The difference is due to the fact when you type and enter, we wait for the local search to return a heuristic result that does the right thing, dropping instead passes the value directly to the urifixup, that doesn't handle a lot of special cases. Unfortunately changing this is not trivial, we could evaluate always waiting for autocomplete to search, though that would add some delay.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
Whiteboard: [fxsearch]
At least in my case, I could live with a delay, since I prefer this to visiting an unwanted page. 

And "abc.de" was caused by: browser.fixup.alternate.suffix where I have ".de" filled. If I remove the value I get http://www.abc/def and server not found. Bit strange, I'd rather expected not any fix up. But this also happens with keyword + Ctrl+Enter.

Should be working correctly now

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.