.....

Ive confirmed it works on the latest 124.0.1 on this machine and 112 which another machine I have is running.

It also doesnt work on 88, which is expected. I suppose there is a cutoff for the older versions where this is an issue. Ill investigate between 90 and 112

Welcome to the real world.  ;-)) Will there be anything else? If not, do mark this issue as resolved and have a simply smashing day. LMAO

89 through 89.02 work when I installed to a different path (thanks for pointing that out, wasnt aware of that option and super helpful for troubleshooting).

Perhaps there is something I customized in the backend that is conflicting with some current google code.

Ill see what I can find out or maybe a fresh install of 89 will solve the issue. Seems like its only an issue on my end so ill resolve this case.

Great. If you're running the pro version of Windows, this is also helpful. https://www.howtogeek.com/399290/how-to-use-windows-10s-new-sandbox-to-safely-test-apps/

For me it fails intermittently with version 89, clearing cookies will sometimes get it working. You could try using User-Agent Switcher to spoof a newer version number.

Version 89 is missing a lot of important security updates though, you should consider switching to the ESR version (115). You can still modify the look of the browser with themes and userChrome.css.

Now that I think about it the problem started after I cleared cookies and cache on both my computers. Maybe something in there was keeping it working on this outdated version.

Yea I really dont like the proton ui but I may have to suck it up. I remember they removed the ability to turn it off in about:config and only briefly tried the css before downgrading back. Hopefully by now people have found a way to get the look and feel as close to older versions as possible.