Greasemonkey is trying to adapt to the model that Firefox 4 is
encouraging/forcing on extensions; trying to get rid of the icon in the
status bar.  This has prompted some rewrites to attempt to support
Firefox 3 as-is for some transition period, while still supporting
Firefox 4 in the newer style.

As part of this work, I more-or-less intentionally broke accelerator
keys for GM_registerMenuCommand().  I've since gone back and forth a few
times as to whether I thought they ever worked correctly, and if I
should continue it a priority to make them work before I call this task
"finished".

So: do you use GM_registerMenuCommand()?  Do you use the accelKey and
accelModifiers parameters?  If so, do you see them _work_?  The best I
have been able to come up with so far is seeing them mostly work, but
rapidly break as I open/close tabs and load pages.  I've never used this
feature myself and I don't know of any good documentation for it.  I'm
starting to consider getting rid of accelerator keys altogether.

So, if you ...
A) Use these features
B) Want these features to remain
C) Can help me understand how this is supposed to work, and prove that
it ever did in the past (a script that runs in Firefox 3.6 +
Greasemonkey 0.8, and a description of how it is supposed to work would
be great)
... Please get in touch with me.

I'd prefer, if possible, that you communicate with the entire
development community at greasemonkey-dev@googlegroups.com .  You can
also email me directly at arant...@gmail.com .  Thanks.

On Tue, Mar 29, 2011 at 6:46 PM, Anthony Lieuallen <arant...@gmail.com>wrote:

The items themselves are for en/disabling behaviour, and I'm unaware of any
(convenient) alternative interface that users could use instead. (Grubbing
around in about:config I don't really consider convenient I'm afraid.)

The script I'm using is available at <
https://code.google.com/p/tdwtfmt/source/browse/trunk/tdwtfmt.user.js>, the
function calls are all near the end.

Selecting an item while using google.com should, after auto-refreshing the
displayed page, toggle the text of the menu item (as well as change the
behaviour of the rest of the script.)

You're reporting a completely different, known, behavior in unreleased
software.  The nightlies are never guaranteed to be working.  You should
not be using them for regular day-to-day work, only if you have reason
to be experimenting with a feature currently in development.

https://github.com/greasemonkey/greasemonkey/issues#issue/1321

(But there's also a chance that the behavior in relation to frames has
changed in the nightlies.  Which would be a second cause of this.  If
you can verify that it's frames, and not something else, causing this
that would be valuable.  Please communicate in the issue linked.)

On Tue, Mar 29, 2011 at 7:42 PM, Anthony Lieuallen <arant...@gmail.com>wrote:

:)

--
PJH

Yes, I use GM_registerMenuCommand, but don't use accelerators and would have
no issue with them not continuing to be available.

I do have a feature request in the area of GM_registerMenuCommand - but will
start a separate thread for that.