is it just me or #Firefox sometimes randomly decides to stop responding to any left mouse clicks on existing tabs? like trying to close, go back or unmute – with no reaction

is it just me or #Firefox sometimes randomly decides to stop responding to any left mouse clicks on existing tabs? like trying to close, go back or unmute – with no reaction

right click and picking an option from the menu works

it started with the last release ig (i'm on 138.0.1, Arch on Wayland)

12 points · 11 comments · view on lemmy.world

11 Comments

bjoern_tantau@swg-empire.de · 2 pts · 1y

I have that as well, guess it is a general problem. Never bothered to mention it to someone.

My whole browser seems to not respond to anything. Switching to another app and switching back usually fixes it.

I guess it's a Wayland thing.

core_of_arden@feddit.dk · 1 pts · 1y

Never any problems. Do you still have that problem when addons are disabled?

SharpLimefox@eldritch.cafe · 1 pts · 1y

@rail_@bark.lgbt i've seen that happen occasionally on sway and i3, and sometimes it was more general (i.e. the entire desktop was no longer responding to clicks but all shortcuts still worked). i don't think I've had it happen to Firefox specifically?

brettm@swarm.coiloptic.org · 1 pts · 1y

@rail_@bark.lgbt i use ctrl+w to close tabs and ctrl+pageUp or ctrl+pageDown to move btwn tabs. Do those keybindings work for you when the mouse won't? I'm on firefox (version 138 i think) on openbsd and haven't seen any change with tabs recently.

ryan_harg@discuss.tchncs.de · 1 pts · 1y

not just you, it happened to mee too, recently.

glimse@lemmy.world · 1 pts · 1y

Never had that but middle click stops working to open new tabs quite often. Might be my mouse though

Boomkop3@reddthat.com · 1 pts · 1y

Not just you, their tabs are shit and they refuse to fix it

Zikeji@programming.dev · 1 pts · 1y

Hmm, maybe some other interaction / conflict? Never experienced this on both my desktop (Arch, Wayland, Gnome) or my work PC (Fedora Silverblue, so Wayland and Gnome but slightly behind).

yoasif@mastodon.social · 0 pts · 1y (2 replies)

@rail_ I saw that recently on Nightly. That makes me think maybe it was package updates.

Is it still happening? Can you make it happen consistently?

rail_@bark.lgbt · 1 pts · 1y (1 reply)

@yoasif@mastodon.social it's happening on a stable release and pretty much every time I use Firefox (but not all the time)

yoasif@mastodon.social · 1 pts · 1y

@rail_@bark.lgbt See if you can figure out mozregression: https://mozilla.github.io/mozregression/

I generally use the CLI version.