Closed
Bug 126924
Opened 23 years ago
Closed 15 years ago
add ability to keep certain URLs in auto-complete memory
Categories
(SeaMonkey :: Location Bar, enhancement)
SeaMonkey
Location Bar
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: vulpine, Unassigned)
Details
It would be nice if bookmarked sites, or sites you flagged, remained in the URL
bar's auto-complete memory. Even if you had not visited in a week (or however
long you set it to last), it would still pop up in the list of close possible URLs.
Comment 2•23 years ago
|
||
I don't think it will, reporter is asking for bookmarks never to
expire from autocomplete no ?
It would certainly help though.
Yes. I think it would be convenient for bookmarked sites (or maybe just
*selected* bookmarked sites) to perpetually remain in autocomplete.
Comment 4•23 years ago
|
||
confirming bug,
Personally i think the solution should be that bookmarks allways appear
autocomplete. I don't think there is a need for any special flagging mechanism
.bookmarking is the flagging mechanism, and anything more would be bloat (my
personal opinion)
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Assignee | ||
Updated•17 years ago
|
Product: Core → SeaMonkey
Updated•17 years ago
|
Assignee: hewitt → nobody
QA Contact: claudius → location-bar
Comment 5•16 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 6•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•