RE: address@hidden: Customizevaluemenudoesn'trecognizemouse-2]

[Drew Adams]

    > IIUC, Richard didn't say that you couldn't let mouse-2 select
    > menu items in the value menu, in addition to opening the menu.

    If we allow that, we will get inconsistent behavior with other menus,
    such as the one that's dropped from the menu bar, because where mouse
    events are handled, we don't know what flavor of menu is being
    processed.

    Allowing mouse-2 on the menu bar is not a good idea, IMO, hence my
    preference above.

So, you seem to be saying that we can't fix the value-menu bug without also
letting mouse-2 do the same thing for the menu-bar. That would be fine - as
I said, it would be good to fix both bugs in such a way that the behavior
was the same. IOW, allowing mouse-2 to both open and choose from a menu-bar
menu would be good, not bad, especially if that was also the behavior for
the value menu.

    > To me, it's OK to not let mouse-2 do either: open or choose.
    > And it's OK to let mouse-2 do both: open and choose. To me,
    > it's not OK to do one but not the other.
    >
    > And, apparently, for Richard it's not OK to not let mouse-2
    > open. So,...

    And to me, it's not OK to let mouse-2 drop menu-bar menus.  So,...

By "drop", do you mean open? If so, what is your reason?

Please don't just state that the only possibility for that would be to
return to the other bug I filed: mouse-2 mistakenly pasting when you tried
to use it to choose a menu item. Is there a good reason that mouse-2
shouldn't both open and choose from a menu-bar menu?