Closed
Bug 260405
Opened 20 years ago
Closed 6 years ago
"Copy Referring Address" context menu item in history
Categories
(Toolkit :: Places, enhancement, P5)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: Biesinger, Unassigned)
References
Details
it would be nice to have a "copy referring address" context menu item in
history, at least if the column is visible; now that we show it (after bug 128398).
rationale: if users see the page that linked them to this page, they may want to
visit it again; to save them from retyping, copying should be supported.
if no referring uri is available, the item should be disabled.
Whiteboard: active
Priority: -- → P5
Target Milestone: --- → Future
Assignee: cst → nobody
OS: Linux → All
Whiteboard: active
Comment 1•20 years ago
|
||
Not quite the same interface, but http://www.squarefree.com/extensions/high/ is
a firefox extension that uses bug 128398 to go to the referring page.
Comment 2•20 years ago
|
||
This could be a nice extension, but having it in the core browser would just
feel like bloat for most users (especially to those who think "Print" shouldn't
be there).
Prog.
Blocks: 135841
Reporter | ||
Comment 3•20 years ago
|
||
Prognathous: why would anyone want a print context menu item in the history window?
No longer blocks: 135841
Comment 4•20 years ago
|
||
I was referring to general context-menu-bloat in Mozilla.
IMHO a "Properties" option for history entries (Bug 199397) is more commonly
needed than "Copy Referring Address". The same is true for page context-manu
with "View Background Image" (implemented) vs. "Print" (wontfixed).
Prog.
Reporter | ||
Comment 5•20 years ago
|
||
"view background image" can only be done via the ctxt menu, while "Print" has a
button and a menu entry (and a keyboard shortcut)... anyway, that does not
belong in this bug
Comment 6•20 years ago
|
||
Allow me to humbly disagree, but since it really doesn't belong in this bug I
won't go into details.
As for what's suggested here, the History feature is mostly intended for
power-users anyway, so I guess another entry in the context menu won't be that
noticeable and won't piss off the purists.
Prog.
Reporter | ||
Comment 7•20 years ago
|
||
maybe it should only be displayed if the referrer column is shown
Updated•16 years ago
|
Component: History: Global → General
Product: Core → SeaMonkey
QA Contact: history.global → general
Updated•16 years ago
|
Priority: P5 → --
Target Milestone: Future → ---
Comment 8•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 9•16 years ago
|
||
This is still a valid enhancement, but now depends on bug 320831 thanks to the switch to the new history backend that broke referer in history support.
Comment 10•16 years ago
|
||
Places history doesn't directly store the referrer (it has something called a visit chain that includes redirects), so I'm afraid this is now invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Component: General → Places
Product: SeaMonkey → Toolkit
QA Contact: general → places
Resolution: --- → INVALID
Comment 11•16 years ago
|
||
Sorry, I didn't see that last comment, I'll reopen and mark the dependency.
Updated•16 years ago
|
Status: REOPENED → NEW
Updated•8 years ago
|
Priority: -- → P5
Comment 12•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: 16 years ago → 6 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•