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)
Firefox
Address Bar
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: cilias, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
2.26 KB,
patch
|
mak
:
feedback+
|
Details | Diff | Splinter Review |
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.
Updated•15 years ago
|
Flags: blocking-firefox3.5?
Updated•15 years ago
|
Keywords: regression,
regressionwindow-wanted
Comment 1•15 years ago
|
||
Don't think this blocks, though I'm pretty sure it's unintentional.
Flags: blocking-firefox3.5? → blocking-firefox3.5-
Updated•15 years ago
|
Flags: wanted-firefox3.5+
Reporter | ||
Updated•15 years ago
|
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
Updated•15 years ago
|
Flags: blocking-firefox3.6?
Comment 2•15 years ago
|
||
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
Reporter | ||
Updated•15 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Version: 3.5 Branch → Trunk
Updated•15 years ago
|
Version: Trunk → 3.5 Branch
Updated•15 years ago
|
Flags: wanted1.9.1.x?
Comment 4•15 years ago
|
||
ranges this regressed: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=ed38105c9c2a&tochange=da613c9fae8c http://hg.mozilla.org/releases/mozilla-1.9.1/pushloghtml?fromchange=e49c05fc9122&tochange=acd2d4638228 => probably by check-in of Bug 485122.
Keywords: regressionwindow-wanted
Comment 5•15 years ago
|
||
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-
Comment 6•15 years ago
|
||
No tests yet.. still compiling.. but I tried it out on a nightly build by modifying components/nsPlacesAutoComplete.js
Comment 7•15 years ago
|
||
Edward, is that patch reviewable yet (presuming you forgot about it ;-)?
Comment 8•14 years ago
|
||
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.
Updated•14 years ago
|
Attachment #399341 -
Flags: review?(mak77)
Comment 9•14 years ago
|
||
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+
Reporter | ||
Comment 10•14 years ago
|
||
-->Trunk Still see this in Fx4 nightlies.
Version: 3.5 Branch → Trunk
Comment 11•13 years ago
|
||
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.
Comment 12•13 years ago
|
||
Bug 494224 remains present in Firefox 5.0 Beta 1. The proposed fix can still be used to rectify the problem.
Comment 13•13 years ago
|
||
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?
Updated•8 years ago
|
Assignee: edilee → nobody
Comment 14•6 years ago
|
||
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.
Description
•