Closed Bug 63823 Opened 24 years ago Closed 14 years ago

Make context menu for "submit" buttons the same as for links

Categories

(SeaMonkey :: UI Design, enhancement)

Product:
SeaMonkey
Component:
UI Design
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED EXPIRED
Milestone:
Future

People

(Reporter: ruairif, Assigned: jag+mozilla)

References

Details

Often when browsing a site, I like to open an interesting link in a seperate 
window, minimise, and return to it later on.
However, sometimes a site might use a button to link to another page. In these 
cases, I lose the context menu functionality which allows me to open in a 
seperate navigator window.

An example of a related problem: a site might link via a button to a PDF file. 
I would prefer to download this file and save for later rather than click the 
button and be forced to use the acrobat plug-in. At the moment, I am unable to 
do this.
Assignee: asa → vishy
Status: UNCONFIRMED → NEW
Component: Browser-General → XP Apps
Ever confirmed: true
QA Contact: doronr → sairuh
Summary: [ RFE ] - Provide context menu functionality for button activated links → [ RFE ] - Provide context menu functionality for button activated links
over to XPApps.
nav triage team:

Yeah, we would like this too, but don't think it's a beta1 stopper. Marking 
nsbeta1-, reassigning to pchen
Assignee: vishy → pchen
Keywords: nsbeta1-
Marking nsbeta1- bugs as future to get off the radar
Target Milestone: --- → Future
OS: other → All
Hardware: Other → All
Summary: [ RFE ] - Provide context menu functionality for button activated links → Make context menu for "submit" buttons the same as for links
Depends on: 75338
marking p4
Priority: -- → P4
Depends on: 17754
->morse, who's now handling context menus.

however, blake, would this be covered by your [upcoming?] context menu patch?
Assignee: pchen → morse
Priority: P4 → --
Target Milestone: Future → ---
Status: NEW → ASSIGNED
Target Milestone: --- → Future
*** Bug 106354 has been marked as a duplicate of this bug. ***
Reassigning to correct component/owner
Assignee: morse → hyatt
Status: ASSIGNED → NEW
Component: XP Apps → XP Toolkit/Widgets: Menus
QA Contact: sairuh → shrir
Target Milestone: Future → ---
Er, no, this is an xpapps level issue.
Assignee: hyatt → blaker
Component: XP Toolkit/Widgets: Menus → XP Apps
QA Contact: shrir → sairuh
Target Milestone: --- → Future
*** Bug 225212 has been marked as a duplicate of this bug. ***
Product: Core → Mozilla Application Suite
Assignee: bross2 → jag
QA Contact: bugzilla
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
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
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
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
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
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
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: 14 years ago
Resolution: --- → EXPIRED
Ever confirmed: true

    
    

    
  
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #16)
> 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.

This bug still applies to Seamonkey 2.6.1. It is a regression from Netscape 4. I would REOPEN it if I could.

It is very confusing and inconsistent the way context menu works for some elements of a page but not for others. The usual way to deal with menu entries that don't apply at the current time is to grey them out or hide them. The odd thing is that all the normal context menu entries for both the page background and for links apply equally to submit buttons, so there doesn't appear to be any reason for there to be no menu.

          You need to log in
          before you can comment on or make changes to this bug.