Closed Bug 1330459 Opened 8 years ago Closed 8 years ago

Detect that inputs like "document.getelementbyid" in the awesome bar are intended as searches and not URLs

Categories

(Firefox :: Search, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1080682

People

(Reporter: dthayer, Unassigned)

Details

Hopefully this isn't a duplicate, but I did try to find it. Searching for documentation as a developer can be frustrating sometimes in Firefox, since common identifiers like "array.prototype.splice" get interpreted as "http://array.prototype.splice/". We should research ways of addressing this. Chromium does not exhibit the same behavior: if you search for "array.prototype.splice" it correctly interprets it as a search. It will however present you with a little "Did you mean http://array.prototype.slice?" window. From what I can tell, Chromium just uses the top-level domain to guess whether you're searching or not (array.prototype.slice.com will be interpreted as http://array.prototype.slice.com/). This seems like pretty reasonable behavior.
I'm sorry, it's a dupe. As a temporary workaround for now, we have added a second entry that does a search, just after the first entry that tries to visit the url.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.