Closed Bug 648394 Opened 14 years ago Closed 13 years ago

Smart keyword for tab search

Categories

(Firefox :: Address Bar, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: sfink, Unassigned)

References

Details

I like having my open tabs in the awesomebar results, but many times I *only* want to search my open tabs. My preferred interface would be a search keyword, since that's how I select all my searches these days (which would be a week after I first learned about the search keyword feature.) I'd want to be able to choose the keyword myself, to make it fit into my own naming scheme. Of course, open tabs is just the main additional type of search. Others are history, bookmarks, and other computers' tabs. I've never personally needed any of those, though.
Which version of Firefox are you using? Is the switch to tab feature in the location bar not enough? When you enter part of the title or URL it should be directly proposed as result in the dropdown.
Component: Tabbed Browser → Location Bar
QA Contact: tabbed.browser → location.bar
writing a "%" char in the locationbar will restrict results to open pages, so like "bug %", there is bug 530209 about improving the preferences in the panel to allow better combinations of what to show in the bar. For other restrictions see browser.urlbar.restrict.* prefs in about:config, you can change the char if you wish.
Depends on: 530209
Starting a search with "% " does exactly what I wanted. I could've sworn mak's "bug %" suggestion didn't work for me when I tried it before, but it seems to now. The only remaining thing I find confusing is that "%foo" doesn't do anything special, which tricked me into thinking it didn't work for a while. I can kind of guess why, but I will offer up one data point that it can be confusing. (I was thinking of % as equivalent to a .* regexp or a * character in a shell pattern match, but it's something else entirely.)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.