Anyone noticing Firefox not letting you use the address bar in some windows?
This is a very recent thing I've had happening, presumably since an update. I will often have multiple FF windows open. In one of the windows, I'll suddenly not be able to place my cursor in the address bar on any tab. But other FF windows function fine. I have to close that window and start a new instance or drag a tab from a working window to another screen, then that will work fine for an unpredictable time.
I have no idea what specific thing I might be doing that touches this off, as far as I can tell I'm just browsing. I thought maybe I had a child dialog opening in a hidden window, but it must be hidden pretty good because I can't find it if I do.
Fedora Linux 42 KDE
Firefox 139.0
LandedGentry
in reply to ikidd • • •asdfsafsafsfa
:::
xylol
in reply to ikidd • • •I've had that happen also, I was trying to close some tabs but they wouldn't close, opening a new window and moving the tabs over made everything work again
I'm on bazzite
RotatingParts
in reply to ikidd • • •chonkyninja
in reply to RotatingParts • • •This fucking bug is not new, and not special to KDE. It’s because there’s missing documentation in a lib just above Wayland, so it only affects some apps that aren’t using a higher level toolkit, Firefox is in that box. The bug is literally 8 years old and would literally require one fucking line of code to fix, but the cunts over at freedesktop refuse to merge the changes. If I were at my main computer I’d send you the link and details.
One thing that sometimes fixes it, is the menu key next to the spacebar.
A Mouse
in reply to ikidd • • •It's probably this bug: bugzilla.mozilla.org/show_bug.…
It's a bug specifically on Wayland.
Try grabbing the tab and moving it and letting go, you don't have to move it's tab slot.
1955112 - Leftover movingtab attribute leaves unresponsive toolbar/urlbar until tab is dragged again
bugzilla.mozilla.orgnfreak
in reply to A Mouse • • •This one's super annoying, I'm glad the tab thing actually fixes it for a bit because I was completely killing my browser every time before I learned about that.
Hope this fix goes live soon