Closed Bug 102941 Opened 24 years ago Closed 16 years ago

Right clicking the color palette causes the menupopup to display

Categories

(SeaMonkey :: Composer, defect)

x86
Windows 95
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: TucsonTester2, Unassigned)

Details

(Keywords: polish)

From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 95) BuildID: 20011002 Right clicking the color palette to select a font or background causes the menupopup to be displayed on the composer window after the color is selected. Reproducible: Always Steps to Reproduce: 1.Open a new composer window 2.Right click the color palette for either font or background 3.Select a color option Actual Results: The menupopup that appears on the composer page just as if you had right clicked the body of the composer page Expected Results: The right click menupopup should only appear if I right click on the body of the composer page, right clicking the color palette should not be linked to the right click body command Win 95 OSR 2.5
tested by right clicking the color palette located on the tool bar
-->cmanske Does this happen on Linux as well or is this windows-specific?
Assignee: syd → cmanske
Target Milestone: --- → mozilla0.9.7
Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.5+) Gecko/20011019
Status: UNCONFIRMED → NEW
Ever confirmed: true
Because of recent core XUL changes, this no longer happens
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Michael/Tucson, please verify..
Status: RESOLVED → VERIFIED
Now that the color picker is back up thanks to fix for 108681, I am able to verify this . . . It looks fine now.
Disregard my last comment, 108681 still appears to be happening.
108681 was fixed, and now this problem is happening again. I am reopening this bug.
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
This will probably go away if I finish converting colorpicker to a menulist.
Status: REOPENED → ASSIGNED
Target Milestone: mozilla0.9.7 → mozilla0.9.9
changing milestone
Target Milestone: mozilla0.9.9 → mozilla1.1
Target Milestone: mozilla1.1alpha → mozilla1.2beta
Keywords: nsbeta1, polish
This isn't happening any more on linux. Is it still happening on other platforms? Should it be nsbeta1+?
Composer triage team: nsbeta1-
Keywords: nsbeta1nsbeta1-
Product: Browser → Seamonkey
Assignee: cmanske → nobody
Status: ASSIGNED → NEW
QA Contact: sujay → composer
Target Milestone: mozilla1.2beta → ---
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: 24 years ago16 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.