FireFox says it is up-to-date, but the reported version is 115.23.0esr (64-bits). The ESR branch apparently is especially made for running on deprecated Windows systems (up to 8.1).
I think it is a bad thing to have pages that don't display correctly on older versions of the browser or OS. Especially since the problem still existed in version 137, which must be a quite recent one if we are now at 138. I can live without an Interactive Diagram for FRC, but it reflects badly on the site if others would encounter this problem.
Do you have any idea what change you made that might cause this? The betzaCSS.js script doesn't seem to have any browser problems on these old systems, and betzaNew.js only has a background problem on Apple devices which seems unrelated. So it must be possible to make a script that runs in this case as well.
BTW, the problem appears on all browsers I tried on this machine (FireFox, Chrome, Edge, the AVG safe browser). So I suppose it has something to do with the plugin JavaScript engine.
FireFox says it is up-to-date, but the reported version is 115.23.0esr (64-bits). The ESR branch apparently is especially made for running on deprecated Windows systems (up to 8.1).
I think it is a bad thing to have pages that don't display correctly on older versions of the browser or OS. Especially since the problem still existed in version 137, which must be a quite recent one if we are now at 138. I can live without an Interactive Diagram for FRC, but it reflects badly on the site if others would encounter this problem.
Do you have any idea what change you made that might cause this? The betzaCSS.js script doesn't seem to have any browser problems on these old systems, and betzaNew.js only has a background problem on Apple devices which seems unrelated. So it must be possible to make a script that runs in this case as well.
BTW, the problem appears on all browsers I tried on this machine (FireFox, Chrome, Edge, the AVG safe browser). So I suppose it has something to do with the plugin JavaScript engine.