Open Bug 198327 Opened 21 years ago Updated 3 months ago

Install a context menu in the autocomplete drop-down list

Categories

(SeaMonkey :: Location Bar, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: rbs, Unassigned)

References

Details

When typed URLs have typos, they hang around in the autocomplete drop-down list
for quite some time. It would be nice if the URLBar's context menu could also
show up in the autocomplete drop-down lis (but with just 'Copy' and 'Delete'
active). This way, the user could remove obsolete URLs.

*** This bug has been marked as a duplicate of 171605 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
This isn't a dupe.  Bug 171605 is for Firebird, and only for the auto-completed
fields, not the location bar.
-> re-opening, I mis-read.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
In addition to the options from the Edit context menu as advocated, other
options could be classic Link options such as "Open in New Window" and "Open In
New Tab".
About the typos being saved, that is bug 9203. And about being able to delete
them, that is bug 87098. Duping.

*** This bug has been marked as a duplicate of 87098 ***
Status: REOPENED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → DUPLICATE
Neither of those have to do with a context menu, though.  Re-opening.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Re-summarizing to avoid further confusion. This bug is about installing a
context menu inside the autocomplete drop-down list (similar to what happens on
the URL field). But with the following suggested options for the autocomplete
context menu:

  Copy               <-- for pasting elsewhere
  Delete             <-- to get rid of an URL with typos in the drop-down list
  ------------------
  Open in New Window
  Open In New Tab
Assignee: hewitt → location-bar
Status: REOPENED → NEW
Summary: context menu in the autocomplete drop-down list → Install a context menu in the autocomplete drop-down list
Somebody suggested an option to clear out the list completely. Maybe "Delete All"?

  ------------------
  Open in New Window
  Open In New Tab
  ------------------
  Copy
  Delete
  Delete All
*** Bug 239396 has been marked as a duplicate of this bug. ***
Blocks: 251874
Product: Core → SeaMonkey
Assignee: location-bar → nobody
QA Contact: claudius → location-bar
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
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: 21 years ago14 years ago
Resolution: --- → EXPIRED
There is no context menu for location bar autocomplete items. Reopening.
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.