v28.15.0, buttons "switched"

[muelli]

Hello forum,

I have a strange problem with Pale Moon 28.15.0 under Linux Mint 20. Sometimes, not always, when I left click an item in a website (link, button, ...) OR Pale Moon itself (menu, new tab, ...) Pale Moon also opens the context menu to that item, as if I clicked the right button.
The left click is recognized and executed, the menu opened, the link followed, etc, but the right button context menu is shown as well.

This is only happening in Pale Moon and not Linux Mint itself...

Any advice, ideas or ways to debug this problem?
Thanks!

[moonbat]

No problems here on Mint 20.

[muelli]

Well what should I say... It is not happening all the time, just sometimes and just in Pale Moon.

edit: I will disable all the running addons to see if there might be something going on behind the curtains....

[Night Wing]

@ muelli

At this time I'm using 64 bit linux Pale Moon 28.15.0 running in 64 bit linux Mint 20 (Ulyana) Xfce. When I click on a link, it takes me straight to the site and never opens a context window to that site.

And I've never seen, on any of my four computers, this happening with any previous versions of linux Pale Moon and I've been using linux Pale Moon since it was first released publicly back in January of 2014.

The problem is on your end someplace and it is not with linux Pale Moon.

[muelli]

You are right, it was in my end. Sorry for the fuzz.
It seems firegestures is not working correctly anymore. Since replacing it with "all in one gestures" this erratic behaviour stopped.
Problem solved!

[moonbat]

As far as possible, look at the Pale Moon addons site first for alternatives to any older Firefox extensions that may have broken over time. The number of extensions for Pale Moon, both ported from Firefox as well as exclusive - has grown considerably over the last few years.

You should look here first and then only at CAA if you don't find what you're looking for. Goes without saying that there is nothing on the post 2017 Firefox addons site that will work because Pale Moon has not and will not support WebExtensions.

[New Tobin Paradigm]

No you should stop using CAA for Pale Moon. You are just setting your self up to be even more irrationally pissed off once old and insecure Firefox extensions are no longer allowed.

[moonbat]

I usually convert them with the target application block for personal use. There are a few more I plan to port for publishing (MPL licensed) but want to convert them to overlay first.

[New Tobin Paradigm]

So you're going to publicly undermine the message we been trying to send for the past year?

You know what the sad truth is? If we ever closed up shop and fucked off into the ether a bunch of you morons would start using crippled XP hackjob builds or deadend fake forks by an adclick company.

You guys really don't do much to convince me that isn't exactly what you deserve.

[moonbat]

I am talking of converting extensions that are legally allowed to be forked into the approved overlay extension format that doesn't cause UI glitches the way bootstrap/jetpack ones do. You know, unlike people who simply take stuff from CAA and expect it to work forever, and who will keep doing it regardless of what anyone here says.

Maybe take some antacids for all that goddamn unwarranted bile you spew at EVERYBODY, including people who have supported this browser and contributed to it far more than and for far longer than I have, and stop fucking getting mad at everything all the time.

[New Tobin Paradigm]

Post repealed and replaced.

I thought about what you said the moonbat and while I think I am still completely correct.. The tone of it was piss poor even for me. So sorry for mostly lash out at you personally.

[moonbat]

All good!