I deem Firefox a bit buggy, but that’s because I use it on platforms that get very little use, And I ain’t got time to hunt bugs down. I barely have the time to report them.
But it’s not people like you and me I’m talking about. It’s people who discovered internet after 2000, who think Firefox doesn’t have enough features, and is “being unreasonable”, because essentially every. single. browser is now chrome or chromium, with the exception of Firefox (and safari?); and because of companies like adobe blaming Firefox for “not playing nice with others” simply because it isn’t chrome/chromium…
Edit: to those who downvoted, which I can only assume is because of my comment on bugs, please install NetBSD 9.3, ctwm, set pkgin up against 2023Q1, and install Firefox 110.0.1 with noscript, umatrix and ublock origin. Now witness how all your menus disappear immediatey as you mouseover upon them. Now please explain to me how this isn’t a bug…
Edit 2: instead of attempting to “backseat debug” without any information on the actual problem, or even without trying to reproduce the bug (I gave all the info I would start with), please accept that Firefox can have bugs, and that people online can know what they are talking about. Thanks.
Sounds to me like some of the third party plugins/extensions you’ve installed are conflicting with one another. That’s not Mozilla’s fault. That can happen to Chrome too.
You’re using several extensions that were all made by different people, and not necessarily designed to interact or be functional together. That’s not a Firefox bug.
Extensions are third party apps and most, if not all, of them are not made by Mozilla. If an unofficial, third party plugin doesn’t work, it’s not up to Firefox to fix that. The issue is with the third party apps.
FF is allowed to change their software, and they’re not at fault if those changes break existing plugins that they had no hand in creating. That’s not how software works.
It works fine with my Cinnamon window manager. So the bug could be in Firefox, in your WM, in both, or more likely in the integration of two, as a side effect, which why I’ve said “on the edge”. It’s nearly impossible to test your software with every combination of a system. So the solution here to file an issue both for WM and Firefox and hope someone from either communities will solve it. Or just get another browser or WM.
I deem Firefox a bit buggy, but that’s because I use it on platforms that get very little use, And I ain’t got time to hunt bugs down. I barely have the time to report them.
But it’s not people like you and me I’m talking about. It’s people who discovered internet after 2000, who think Firefox doesn’t have enough features, and is “being unreasonable”, because essentially every. single. browser is now chrome or chromium, with the exception of Firefox (and safari?); and because of companies like adobe blaming Firefox for “not playing nice with others” simply because it isn’t chrome/chromium…
Edit: to those who downvoted, which I can only assume is because of my comment on bugs, please install NetBSD 9.3, ctwm, set pkgin up against 2023Q1, and install Firefox 110.0.1 with noscript, umatrix and ublock origin. Now witness how all your menus disappear immediatey as you
mouseoverupon them. Now please explain to me how this isn’t a bug…Edit 2: instead of attempting to “backseat debug” without any information on the actual problem, or even without trying to reproduce the bug (I gave all the info I would start with), please accept that Firefox can have bugs, and that people online can know what they are talking about. Thanks.
Sounds to me like some of the third party plugins/extensions you’ve installed are conflicting with one another. That’s not Mozilla’s fault. That can happen to Chrome too.
You’re using several extensions that were all made by different people, and not necessarily designed to interact or be functional together. That’s not a Firefox bug.
Yeah sure, the exact same set of extensions that worked with 102, and they also work with 110 on other OSes. Must be that…
Extensions are third party apps and most, if not all, of them are not made by Mozilla. If an unofficial, third party plugin doesn’t work, it’s not up to Firefox to fix that. The issue is with the third party apps.
FF is allowed to change their software, and they’re not at fault if those changes break existing plugins that they had no hand in creating. That’s not how software works.
Look like a bug on the edge of WM/App
Yeah well, Firefox is the only GUI software that shows this behavior, and it wasn’t present with 102. The only thing that changed was Firefox.
It works fine with my Cinnamon window manager. So the bug could be in Firefox, in your WM, in both, or more likely in the integration of two, as a side effect, which why I’ve said “on the edge”. It’s nearly impossible to test your software with every combination of a system. So the solution here to file an issue both for WM and Firefox and hope someone from either communities will solve it. Or just get another browser or WM.