Chromium legacy

#276 @Wowfunhappy I appreciate the continued maintenance on the Chromium Legacy app. I have various machines running macOS 10.7 Lion through Big Sur (2020 MBA). I've enjoyed the usability, functionality and compatibility that Chromium Legacy provides on the older machines. By the way, the old method (attached) for suppressing Google's obnoxious infobar to upgrade the operating system no longer works in newer versions of Google Chrome on Mac OS, and I haven't found a solution for Mac even though someone found a solution for Windows via the registry (Disable or Remove Unsupported OS Warning in Chrome and Edge on Windows 7 and 8.1) View media item" href=" target="_blank"> chrome49.png 578.4 KB · Views: 325 #277 @Wowfunhappy I appreciate the continued maintenance on the Chromium Legacy app. I have various machines running macOS 10.7 Lion through Big Sur (2020 MBA). I've enjoyed the usability, functionality and compatibility that Chromium Legacy provides on the older machines. Don't thank me, I just made a little updater PrefPane! Chromium Legacy is maintained by Bluebox (who isn't a member here).Bluebox accepts donations via Github sponsors. If you appreciate Bluebox's work, please consider donating! Last edited: Dec 29, 2022 #278 I've installed Chromium 89.0.4333.0 ( 829983.zip ) from github.com/blueboxd/chromium-legacy/releases?page=99 on my Mac OS X 10.7.5 It works quite fine except one thing: It doesn't have the regular close/minimize buttons on top left. Is this normal? #279 For the early versions yes. Eventually those got fixed. Try a newer release. #280 @Wowfunhappy>and modern websites often need more

Of chromium-legacy with the downloader and it asked me to install the ISRG Root X1 Certificate. Once I did this the two pop ups with "chromium would like to use your location" and "Chromium wants to use your confidential information..." came up. So I guess that's why I wasn't getting the pop up after I cleared my certificates. #294 I just downloaded the new version of chromium-legacy with the downloader and it asked me to install the ISRG Root X1 Certificate. Once I did this the two pop ups with "chromium would like to use your location" and "Chromium wants to use your confidential information..." came up. So I guess that's why I wasn't getting the pop up after I cleared my certificates. Yeah, those are the first two. The third is "Do you want the application “_Chromium” to accept incoming network connections?" (yet Chromium is already listed in Firewall to accept them). Last edited: Mar 31, 2023 #295 I've been running Chromium 111 for quite a while so I decided to upgrade to the latest stable build (114). Unfortunately I got a 'Download failed...' message for the first time ever, and the same happened whatever build I chose.Is there anything I should know?ETA I downloaded v114 direct from Github and it's running ok. Last edited: Jun 12, 2023 #296 I've been running Chromium 111 for quite a while so I decided to upgrade to the latest stable build (114). Unfortunately I got a 'Download failed...' message for the first

(clicking the checkbox to stay logged in). But after quitting and re-opening Chromium I'd have to log back in every time. This was with absolutely no change of the settings in Chromium, no login to a Google account, no extensions. A completely stock install. It was acting as if I was in Incognito mode, but I was not.I tried to mitigate this somewhat by saving the passwords using the built-in password manager, but that seemed to be disabled and/or broken as well. It never popped up to offer to save anything, and if I tried to save a password manually in the password manager settings it never actually saved.This was on a MacMini2,1 running fully up-to-date Lion (10.7.5). Very vanilla installation--in fact I tried completely erasing the system disk and reinstalling Lion from scratch. Chromium Legacy was the very first app in installed, and the same problems occurred.If I instead install Chromium legacy manually from the github page, neither of these problems occur (i.e. cookies work, as does the native password manager), so I have to assume the problem relates to the customization performed by @Wowfunhappy 's installer. I did search this thread and the discussion over at the github and couldn't find any mention of these issues, though. So maybe it's something unique to this model (or to Lion, which is probably not being used much by other people these days--it's the last supported OS for MacMini2,1 though).Happy to test anything if you have any ideas for fixing this.