Closed
Bug 10191
Opened 25 years ago
Closed 25 years ago
[RFE] User access to Back/Forward URL buffer
Categories
(SeaMonkey :: UI Design, enhancement, P3)
SeaMonkey
UI Design
Tracking
(Not tracked)
People
(Reporter: Crysgem, Assigned: don)
Details
I know not the intent for continuing v4.x atavisms into Mozilla-based browsers,
but, submitted for your visualization: The visited-URL menu that appears when
one depresses and holds the "Back" or "Forward" buttons. The same, appearing
when one selects the "Go" menu option. Desired: The ability to edit those URLs,
insert new ones, to rearrange and to delete them. Implementation would obviously
require that the menus remain extruded even after a user action/"event". To
avoid newbie shock, perhaps some design would seperate the scribe menu from the
static one. <Winks to the XUL crowd>
~~Implementation details: Ignore if uninterested~~
The scribe menu and static menu would differ thus: The static menu would
essentially duplicate the form of 4.x's visited-URL menu. The scribe menu would
display both the <Title> data of the document listed and the full URL (or
perhaps, by color-coding URLs of each protocol, as HTTP/FTP/gopher, obviating
the need of displaying the protocol in the menu).
Comment 2•25 years ago
|
||
Why would anyone ever ever want this? I just don't get it. The only people I can
think of who'd possibly use it would be malicious Webmasters, trying to change
the menus remotely.
Comment 3•25 years ago
|
||
I think bug 39245 takes this one step further and more useable, will post color-
coding-idea of this one to 39245
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
Comment 4•25 years ago
|
||
will reopen again to marks as DUP
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 5•25 years ago
|
||
marking dup
*** This bug has been marked as a duplicate of 39245 ***
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•