Closed Bug 494224 Opened 15 years ago Closed 6 years ago

Star is not displayed in location bar list items when clicking dropdown arrow

Categories

(Firefox :: Address Bar, defect)

defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: cilias, Unassigned)

References

Details

(Keywords: regression)

Attachments

(1 file)

Build identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1pre) Gecko/20090521 Shiretoko/3.5pre

My guess is that this is a regression from bug 485122.

I have the location bar set to display both bookmarks and history. If I click on the dropdown arrow on the location bar (not typing, just viewing the top items), there is no star displayed beside entries which are bookmarks.

I've only tested on Shiretoko/Mac.
Flags: blocking-firefox3.5?
Don't think this blocks, though I'm pretty sure it's unintentional.
Flags: blocking-firefox3.5? → blocking-firefox3.5-
Flags: wanted-firefox3.5+
Summary: Star is not displayed in location bar when clicking dropdown arrow → Star is not displayed in location bar list items when clicking dropdown arrow
Flags: blocking-firefox3.6?
It's the same in WinXP.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090521 Minefield/3.6a1pre ID:20090521043940
OS: Mac OS X → All
Hardware: x86 → All
Version: 3.5 Branch → Trunk
Version: Trunk → 3.5 Branch
Flags: wanted1.9.1.x?
We should fix this in 1.9.2.
Flags: wanted1.9.1.x?
Blocks: 485122
I agree that we should fix it; in the future, you should feel free to assign regressions to their regressors, as I've just done.

Mardak: can you restore this functionality, please?
Assignee: nobody → edilee
Flags: wanted-firefox3.6+
Flags: blocking-firefox3.6?
Flags: blocking-firefox3.6-
Attached patch v1Splinter Review
No tests yet.. still compiling.. but I tried it out on a nightly build by modifying components/nsPlacesAutoComplete.js
Edward, is that patch reviewable yet (presuming you forgot about it ;-)?
I can confirm that the patch by Edward solves the problem. But I recommend using a new function _hasDefaultBehaviour to retrieve the default autocomplete behaviour instead of adding a parameter to _hasBehaviour for code clarity.
Attachment #399341 - Flags: review?(mak77)
Comment on attachment 399341 [details] [diff] [review]
v1

the proposed change is correct (f+), but I second the request in comment 8 for a new hasDefaultBehavior method, plus this should have a test (r-).
Attachment #399341 - Flags: review?(mak77) → feedback+
-->Trunk
Still see this in Fx4 nightlies.
Version: 3.5 Branch → Trunk
The bug is still present in the official Firefox 4.0 release despite a working fix being available for almost one year now. The proposed fix still works with Firefox 4.0 by applying the diff to the new version of nsPlacesAutoComplete.js.

To emphasize, the described bug occurs *only* when using the pulldown menu. It explicitly does not occur when typing and getting suggestions.
Bug 494224 remains present in Firefox 5.0 Beta 1. The proposed fix can still be used to rectify the problem.
After further investigation, the cause of this bug lies in the restriction of "empty searches" (i.e. searches for ""). By default, search results of empty searches are restricted to previously typed and visited urls. Using the pulldown menu button of the url bar also counts as "empty search".

With this new information, the correct solution would be to differentiate between an "empty search" and using the pulldown menu button, and only applying the restrictions to the former. As to how, I currently do not know.

Meanwhile, an easy userland bypass is to set default.behavior.emptyRestriction = 0 (no restrictions) or = 32 (url must have been typed previously). But this also affects true "empty searches".

Still, a general design question remains:
If the shown results are restricted to the history, should the star symbol indicating bookmarked urls be explictly hidden (current design) or not?
Assignee: edilee → nobody
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: