Closed
Bug 657338
Opened 14 years ago
Closed 7 years ago
Awesomebar should search open tabs first.
Categories
(Firefox :: Address Bar, enhancement)
Firefox
Address Bar
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: bugzilla, Unassigned)
References
Details
(Keywords: uiwanted)
Awesomebar can at times be slow, especially with lots of history.
If I search for a phrase in the awesomebar, it can come up with suggestions, before mentioning that there is an open tab that matches.
Open tabs should be searched first - rather than popping up somewhat randomly in the list during the period of a several second search.
Comment 1•14 years ago
|
||
Maybe not a duplicate, but at least it affects how bug 546254 may be implemented.
OS: Linux → All
Hardware: x86 → All
Version: 4.0 Branch → Trunk
Comment 2•14 years ago
|
||
We do actually search it first, FWIW.
Comment 3•14 years ago
|
||
I'm constantly getting results that don't include open tabs. I think I'm seeing what Ian is.
Comment 5•13 years ago
|
||
I understand that for devs this can be frustrating if you have a bunch of bug tabs open, but if you get a bunch of open tabs you can keep typing til you find the one you want.
In my case I don't realize I already have tabs open. I currently have 2 facebook tabs open but it only tells me about 1 of them, which is an improvement. I've seen it not tell me about any. This happens frequently with sites I go to a lot of pages on, google, youtube etc. I know I can add % but that's only if I already know I have the tab open.
IMO the point of this feature is to help you not open duplicate tabs so it should definitely tell you when you have open tabs that match your search. Not sure what the right balance is. Maybe a pref for people like devs? Or a more discoverable switch to exclude open tabs?
Comment 6•7 years ago
|
||
If a search is taking multiple seconds, we should look into that, rather than wallpapering the problem. Feel free to reopen if this still is a problem.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•