Closed Bug 1067922 Opened 11 years ago Closed 2 years ago

Correctly handle path-like inputs like "t:" in autocomplete

Categories

(Toolkit :: Places, defect, P3)

Product:
Toolkit
Component:
Places
Type:
defect
Points:
8

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: Unfocused, Unassigned)

References

Details

Caught in bug 951624 comment 45. Paolo found that typing "t:" resulted in a result for "Visit http://www.google.com/search?q=t:...". On Windows, "t:" is the start of a valid path. On unix-like OSes, it is not a valid path.
Flags: qe-verify+
Flags: firefox-backlog+
QA Contact: andrei.vaida
Ah-ha! We handle this correctly on Window, where we see it as a path and over to navigate to file:///t:/ However, on Linux this isn't a valid path. And nsDefaultURIFixup is returning a keyword search - even though we said we don't want to use that. So this is a bug in nsDefaultURIFixup.
Er, to clarify: That's both Linux and OSX. Anything non-Windows.
Priority: -- → P3
Severity: normal → S3

This is platform-dependant, and I think it's working as expected.

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