Has anyone noticed an interface/performance difference on BGA and some other sites between Firefox 140 and Firefox 141 under Windows?
I've noticed that on pages where there are dynamic elements, on Firefox 141.0 I'm seeing the pointer rapidly cycle between different pointer types (normal arrow, pointing finger that indicates a clickable link, text box interaction vertical bar with serifs) and delays on user interface action. I reinstalled Firefox 140.0.4 in parallel to compare the behaviour, I'm not seeing it there so it seems to be a Firefox problem rather than something else. BGA happens to be the site I see it most obviously on, particularly in Lobby with options set to Simple Game/Real-Time/Manual where the number of available tables per favourite game updates frequently.
To be clear, I currently think this is a FF issue not a BGA bug, hence not logging it as such. But thought that it's easier to get some independent confirmation from others in BGA community before I log it as a bug with FF, to ensure it's not something on my end.
(Besides reinstalling FF140 for checking, I've also checked Chrome browser (bad behaviour not observed) and used FF141 Troubleshooting mode (bad behaviour observed))
Thanks
Tim
I've noticed that on pages where there are dynamic elements, on Firefox 141.0 I'm seeing the pointer rapidly cycle between different pointer types (normal arrow, pointing finger that indicates a clickable link, text box interaction vertical bar with serifs) and delays on user interface action. I reinstalled Firefox 140.0.4 in parallel to compare the behaviour, I'm not seeing it there so it seems to be a Firefox problem rather than something else. BGA happens to be the site I see it most obviously on, particularly in Lobby with options set to Simple Game/Real-Time/Manual where the number of available tables per favourite game updates frequently.
To be clear, I currently think this is a FF issue not a BGA bug, hence not logging it as such. But thought that it's easier to get some independent confirmation from others in BGA community before I log it as a bug with FF, to ensure it's not something on my end.
(Besides reinstalling FF140 for checking, I've also checked Chrome browser (bad behaviour not observed) and used FF141 Troubleshooting mode (bad behaviour observed))
Thanks
Tim