If someone gets into this discussion, I recommend that you simply comment out all the GNOME styles so that this does not happen again in the future.
Just comment that line in your userChrome.css file
import “firefox-gnome-theme/userChrome.css”;
You can found it here:
/home/YOUR_LINUX_USER_NAME/.mozilla/firefox/YOUR_PROFILE/chrome/userChrome.css
Seems to be userChrome.css doing that. Which would explain why I have never seen it but I do want to do custom CSS so this may pop up for me too.
You’re using an unusual desktop environment or something it would seem. Why haven’t I seen that, ever, in several different distros and DEs? You truly are willing to call a software trash because it doesn’t support a niche setup…?
You’re using an unusual desktop environment
Hyprland isn’t niche. It used to happen on Gnome wayland as well, but I don’t have any machines with it anymore.
What do you get for being a pedantic ass arguing people’s lived experiences on the internet? Seriously? Do you seriously feel butt hurt when someone has a bad experience with something you like, so you make it your life mission to attack and invalidate them? It’s sad, just stop.
I’m not attacking a lived experience. I’m saying that you’re wrong that Firefox is completely broken. It isn’t. You revealed one thing that is arguably a bug. Instead of understanding that most people never experience that, you choose to spout off and invalidate millions of hours of effort toward a more open Internet. This one thing that literally might not even be a Firefox problem doesn’t mean it’s entirely broken, even if it is 100% a FF bug.
Focusing the address bar opens a result pane - it’s supposed to render under the address bar, but for some reason it renders overtop: https://www.reddit.com/r/firefox/s/Fsqmy31fve
From the link:
Seems to be userChrome.css doing that. Which would explain why I have never seen it but I do want to do custom CSS so this may pop up for me too.
I’ve literally never seen that. That post is from years ago too so I’m far from convinced it was more than just a blip.
It’s literally a known issue.
Here, let me install Firefox fresh and see what happens. Yup, still there. So much for your “blip” theory.
You’re using an unusual desktop environment or something it would seem. Why haven’t I seen that, ever, in several different distros and DEs? You truly are willing to call a software trash because it doesn’t support a niche setup…?
What do you get for being a pedantic ass arguing people’s lived experiences on the internet? Seriously? Do you seriously feel butt hurt when someone has a bad experience with something you like, so you make it your life mission to attack and invalidate them? It’s sad, just stop.
I’m not attacking a lived experience. I’m saying that you’re wrong that Firefox is completely broken. It isn’t. You revealed one thing that is arguably a bug. Instead of understanding that most people never experience that, you choose to spout off and invalidate millions of hours of effort toward a more open Internet. This one thing that literally might not even be a Firefox problem doesn’t mean it’s entirely broken, even if it is 100% a FF bug.