[Greasemonkey] [Help]How to replace an js method or event?

[Bill Donnelly]

It's *typical* that the "bug" was marked "RESOLVED WONTFIX".
I generally try not to 'dis' Ffx programmers, and other Open Sourcers,
and other programmers, in general, but, again, it's not THAT difficult.

If you don't want an event handler triggering other events and
handlers, then STOP them. Simple. (if you don't understand how
to do that, then you should NOT be working on Firefox, just as
many people who are, really shouldn't be, but, it's an open source
project, and people are donating their time and such, so what are
you going to do? -- the answer to that should be evident, but it is
rarely exercised, and definitely not exercised enough, imo)

If there is a 'problem' with multiple and/or nested events being
triggered and modifying the global event object values, then that
is just the way it is (and probably should be). The onus is then on
the programmer to decide how they want to proceed and/or
take care of any weirdness that may, or may not, occur when they
decide they want or need to access the object values. As long as
it is documented and understood that something works a certain way.

But that DOES NOT mean you decide to just not support it at all.
(although it is a good way to NOT work, which I've seen more of
in my life by certain 'types' than I would have liked to see --- also,
it is a good way to not work on something you don't understand,
and/or is too difficult for you -- just say, "Nope." ('not a good idea',
'not doable', 'would take too long', what-ev-er), and hope someone
(who theoretically and ideally knows what they're doing and talking
about) doesn't call you on it.

I have already written an example of the code (more or less) that
'corrects' the problem, just not in the way it really should be done,
and where it should be done. If I was a Firefox programmer, I would
fix it. And maybe even do it in a better way, or the "right way", ideally.
This GmScript is a nice, quick work-around that is better than nothing.

If I get some time, I might do some Ffx work, and this might be one
of the things I do, although I know the internal project politics and egos
and incompetence and ineptitude and such within the Firefox project,
and similar programs and projects, pretty much makes it not worth the
trouble and irritation. That crap is bad enough to have to deal with
when you are being paid. (usually severely underpaid)

Again, regardless of what strangeness does or can occur in IE,
or Visual Basic, or whatever programming language, it is better
to have it and have it work the way it does than to not have it at all.

I think that should be *self-evident*.