156054 - AIM contextual menu plug-in adds itself to every drop-down

Status: RESOLVED INCOMPLETE

(Camino Graveyard :: HTML Form Controls, defect)

Description

[Mark Setzer]

Using Chimera nightly from 07-06-2002:

Whenever a pulldown menu from a page form is accessed, with AOL's AIM Contexual
Menu plugin installed, the AIM hierarchial menu displays itself as the last list
option. This is reproducible in the latest nightly on sites like bugzilla. I am
running OS X 10.1.5.

Comment 1

[Mark Setzer]

whoops, that's chimera nightly from 06-29-02, unfixed as of 07-05-02. 

Comment 2

[James]

Recommend INVALID because the AIM CMM plug-in behaved like this under OS 9 and
is the major reason I never have it enabled.

Comment 3

[Mark Setzer]

you sure this is an AOL issue? other Cocoa browsers (OmniWeb for sure) and
carbon ones (Mozilla in particular, but also IE) that use "native" OS widgets do
not behave this way.

Comment 4

[Lewis Francis]

This also occurs when clicking on the empty space of a pick-list like the cc
field on this bugzilla form.

Comment 5

[Greg K.]

*** Bug 170138 has been marked as a duplicate of this bug. ***

Comment 6

[gc]

This happens with all Contextual Menu Items (I have it with Launch Items), and
only in Chimera, even the last builds of 09/30 (I have tested with IE, iCab,
Omniweb, Opera, Mozilla 1.2a)

Comment 7

[Tomasz Kukielka]

This bug affects OnMyCommandCM 1.5.3 when the context of a command is set to
"show always". OnMyCommandCM is available at:
http://free.abracode.com/cmworkshop/
A sample plug-in (with sources) demonstrating the problem is available at:
http://www.abracode.com/EmptyCM.dmg.gz
A screenshot with popup button showing a menu with additional unwanted item is
available at:
http://www.abracode.com/CaminoCMBug.pdf
If developers of Camino need additional information on how the bug is triggered,
please e-mail me. Abracode plans to release more contextual menus which are
showing "always" so this problem will be returning.

Comment 8

[Mike Pinkerton (not reading bugmail)]

yeah, this is cuz we use context menus for our popup menus. we need to find a
way around this at some point. we have other bugs because of this

Comment 9

[Samuel Sidler (old account; do not CC)]

Is this still true? I'm honestly not sure what the AIM contextual menu is... ;)

Comment 10

[Simon Fraser [no longer active]]

Yes, still true.

Comment 11

[Samuel Sidler (old account; do not CC)]

I don't see this as blocking 1.0 since there hasn't been any progress in figuring out it's cause or a fix.

Pushing to 1.1.

Comment 12

[Stuart Morgan]

Moving to 2.0, since depending on how things go with core widgets we might switch over to non-native select menus then.

Comment 13

[Chris Lawson (gone)]

My comment from another recent CM bug:

Can we possibly use

http://waffle.wootest.net/2007/08/07/popping-up-a-menu-in-cocoa/

to make our menus a little more bulletproof?

Note, in particular:

"So, in other words, whenever I get a rashly coded menu shown to me, it also
gets the invaluable, or not, 'Add to Google Calendar' menu item affixed to it,
on account of me having the Google Notifier installed."

It seems as though this is suggesting a means by which we could prevent things
from showing up in our context menus which have no business being there. For
instance, it doesn't seem like SpringyCM's functionality has any utility in the
menus where it was triggering this crash. (The same applies to AIM, OnMyCommand, etc.)

This may not be a meaningful approach with widget code, but it does seem like it might be useful for native CMs in the chrome.

Comment 14

[Stuart Morgan]

That sounds like a good option to explore, since we aren't going to be switching to core menus for selects.

Comment 15

[Takanori MATSUURA]

This bug lies at rest in the graveyard.