Closed
Bug 1432876
Opened 8 years ago
Closed 8 years ago
Searching for string 'Services.prefs.getBoolPref' in unified bar shows trouble finding site
Categories
(Firefox :: Search, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1080682
People
(Reporter: pdahiya, Unassigned)
Details
Searching for string 'Services.prefs.getBoolPref' in unified bar shows trouble finding site
STR:
1. Type search string 'Services.prefs.getBoolPref' in unified bar and hit enter
Actual Results:
Search fail with displayed message 'Hmm. We’re having trouble finding that site.'
Expected Results:
Should show search results using user preferred search engine
Comment 1•8 years ago
|
||
we don't know if what you typed is a string to search or a domain, due to the lack of bug 1080682. For now what we are doing is adding a Search for option, it should be the second entry in the popup.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
| Reporter | ||
Comment 2•8 years ago
|
||
(In reply to Marco Bonardo [::mak] from comment #1)
> we don't know if what you typed is a string to search or a domain, due to
> the lack of bug 1080682. For now what we are doing is adding a Search for
> option, it should be the second entry in the popup.
cool, noticed second entry option in nightly. I still believe with unified bar we need to rethink the message we are showing
“Hmm. We’re having trouble finding that site. We can’t connect to the server at www.date.gettime.
If that address is correct, here are three other things you can try:....”
to something that helps users with these unruly search strings, may be something like
“Hmm. We’re having trouble finding that site.
Did you mean to search date.getTime?
We can’t connect to the server at www.date.gettime. If that address is correct, here are three other things you can try:...”
where search date.getTime is a link or button that queries '?date.getTime'
| Reporter | ||
Updated•8 years ago
|
Flags: needinfo?(mak77)
Comment 3•8 years ago
|
||
A long discussion about improving usefulness of error pages happened in the past in bug 482874, and you suggestion should likely be part of that. Unfortunately looks like it didn't get traction, but it's possible our UX team is still looking into the problem.
You could file an enh request and make it block that bug. You could also needinfo bbell or some other UX team member on it.
Flags: needinfo?(mak77)
| Reporter | ||
Comment 4•8 years ago
|
||
Thanks filed bug 1433991 for UX feedback.
You need to log in
before you can comment on or make changes to this bug.
Description
•