Closed
Bug 483133
Opened 16 years ago
Closed 16 years ago
Address/URL/awesome bar is not honoring matchOnlyTyped flag.
Categories
(Firefox :: Address Bar, enhancement)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: void.at, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3
I have matchOnlyTyped set to true. But Fx 3.1 b3 is not abiding by it, showing all the history in it.
BTW, I also read it shouldn't display (non-bookmarked?) javascript: links, but it did the first time I ran it. I deleted it (shift+del) and now it's only showing my bookmarked ones (which I don't like either) even though I have entered a couple of them.
Reproducible: Always
Steps to Reproduce:
1. set the flag to true
2. browse through a site
3. write the domain in the url bar again
Actual Results:
All the visited pages in that domain are listed.
Expected Results:
Only the entered url shoul appear.
P.S. Is this the right place for beta versions reports?
Summary: Awesome-bar is not honoring matchOnlyTyped flag. → Address/URL/awesome bar is not honoring matchOnlyTyped flag.
Comment 1•16 years ago
|
||
It's not a supported pref, we didn't support it in firefox 3.0 either.
There's a number of prefs to tweak what results are returned, a google search will tell you how to tweak to get the behaviour you want.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Yes, and they will point me to matchOnlyTyped —want to try?.
Care to share the tweak you mention, URL and/or keyword to find it?. I've found matchBevaior and the match.* characters, but none of those seem to do the same —not to mention the latter is far from practical for an always-wanted behavior.
Comment 3•16 years ago
|
||
Ah, the joy of "shared wisdom"
This isn't a support forum, but filtering on visitbonus in about:config will let you zero out everything that isn't typed, if you really want such a limited version of the feature.
I see, it doesn't seem to be "common knowledge" yet. Sorry for the bother and thank you very much for your reply.
Since it was an unsupported feature, I guess you won't mind if I change it to an "enhancement"... right?
Severity: normal → enhancement
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Comment 5•16 years ago
|
||
It is supported...
browser.url.behavior
You want it set to 32, which will match only typed. See the rest of the flags here:
http://mxr.mozilla.org/mozilla-central/source/toolkit/components/places/src/nsNavHistory.cpp#326
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → WORKSFORME
Comment 6•16 years ago
|
||
Yes, I will, since it's a request to implement support for a hidden pref that duplicates existing options. Unnecessary code bloat, overall.
Resolution: WORKSFORME → WONTFIX
Thank you, Shawn. I set browser.urlbar.default.behavior to 32 and I got the behavior I wanted (now I need to undo everything else I did).
Mike, you're talking about code. But right now I'm just a user requesting a feature —it's great to be on the 'blind' side :)
Comment 8•16 years ago
|
||
Features == code. If we added a pref for everything someone wanted, it'd be near-impossible to maintain the codebase. :)
I see your point. Since there is already a way to do it, which just happens to be more customizable, there's no real meaning in having it there.
If I also knew a bit about UI or design, then I could probably go like "Yes, there's no meaning in having two things to do the same. Furthermore, it could trouble users and developers by having to identify which has precedence".
I have a couple more of questions but I rather go to a support forum, right Mike?
Thank you both for your time.
You need to log in
before you can comment on or make changes to this bug.
Description
•