Because I upgraded my Mac (from 2011 to 2017) I've had to upgrade from Mavericks to High Sierra. Unfortunately, though Chromium opens with all my tabs, none of the pages will load (though they do in Firefox Dynasty). What’s causing this?.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Other Chromium Legacy: Google Chrome for OS X 10.7 – 10.9
- Thread starter Wowfunhappy
- Start date
-
- Tags
- web browsers
- Sort by reaction score
iPodNano3
macrumors 6502
you may have to hit enter in the address bar a couple times, chromium has this weird issue where it just randomly goes blank or just doesnt load at all
No, it’s not that (I experienced that in Mavericks!). There is nothing that will make any page load - repeatedly hitting the address bar, clicking ‘Reload this page’, or anything else. I even tried launching Jonathan’s preference pane and download v121 instead, but the same thing happens there too.
This is very odd. I know Legacy wasn't designed for High Sierra but I can't think of any reason why it doesn't load pages.
Further information:
I tried another user account, and at first I thought it was working because it gave me the Google search home page. Unfortunately, as soon as I typed a search and hit return, nothing happened. Everything appears to work except Return isn't recognised and therefore pages won't load.
HOWEVER… I had an old version (v111) knocking around, and that works! So how is it that Legacy 111 works in High Sierra but 121 and 124 don't but they do in Mavericks?
So what I will do, is download every version of Legacy from 111 onwards with the Preference Pane until I find the version that no longer works, then report back.
I tried another user account, and at first I thought it was working because it gave me the Google search home page. Unfortunately, as soon as I typed a search and hit return, nothing happened. Everything appears to work except Return isn't recognised and therefore pages won't load.
HOWEVER… I had an old version (v111) knocking around, and that works! So how is it that Legacy 111 works in High Sierra but 121 and 124 don't but they do in Mavericks?
So what I will do, is download every version of Legacy from 111 onwards with the Preference Pane until I find the version that no longer works, then report back.
Last edited:
Well, I didn't have to look far. The oldest build in the Pane is v115 and that behaves just like v124 - doesn't load any pages.
So that leaves one question : was there a change in the Preference Pane after v111 that might have affected how the app behaves in High Sierra? I only ask because I've obviously had v111 since way back when, so it would have been downloaded using an old version of the Pane. @Wowfunhappy - what are your thoughts?.
So that leaves one question : was there a change in the Preference Pane after v111 that might have affected how the app behaves in High Sierra? I only ask because I've obviously had v111 since way back when, so it would have been downloaded using an old version of the Pane. @Wowfunhappy - what are your thoughts?.
uacd
macrumors 68000
I’ve got a fun lifehack for all the people trying to browse the web on old systems such as 10.7-10.9!
All you need is… to browse from Windows virtual machine. Yeah. Complicated but you get most sites working even on ancient Windows XP and ESR Firefox. Even YouTube videos seem to load normally. I use Parallels, so you need to get relevant version somewhere, as well as Windows distribution. You can use any Windows you are able to install, up to 8.1.
My setup is iMac late 2012, Mountain Lion (10.8). Running off external HDD btw, internal has been dead for more than 10 years already
All you need is… to browse from Windows virtual machine. Yeah. Complicated but you get most sites working even on ancient Windows XP and ESR Firefox. Even YouTube videos seem to load normally. I use Parallels, so you need to get relevant version somewhere, as well as Windows distribution. You can use any Windows you are able to install, up to 8.1.
My setup is iMac late 2012, Mountain Lion (10.8). Running off external HDD btw, internal has been dead for more than 10 years already
Hughmac
macrumors 603
I don't understand why Chromium is not working for you in High Sierra, as I have the latest v127 from May 2024 working fine on a mid 2010 unibody Macbook A1342 with Mojave, patched by the dosdude1 method.
I'm not trying to rub it in, just letting you know it's possible to run the latest version in HS or later.
I also have 16GB RAM and 1TB SSD, but obviously my graphics are totally different.
Cheers 🙂
Hugh
Well, Chromium Legacy v111 IS working for me, but all builds from v115 onwards are not, so I'm suspecting that it may be something to do with the Preference Pane. My final test will be to download v124 direct from the GitHub page (bypassing the Pane), and see if that works.
SUCCESS! I downloaded Legacy v127 direct from the GitHub page and it’s working fine. It MUST be something unintended to do with the Preference Pane after all - which can perhaps be explained by its original intent to be for OS X 10.7 - 10.9; clearly there's something in 10.13 which breaks it somehow.
Last edited:
My thoughts are, please do not use my Preference Pane on anything newer than OS X 10.10. I do not design for or test those versions and I do not know what will happen. Anything that works is a happy accident.
I didn't realise! But I'm glad it all worked out in the end.
What about your Pane for FF Dynasty - should that also be avoided in 10.13?.
It's simpler so it might work fine—but basically I don't know, I don't test on those operating systems and I'm not going to fix any problems that arise (unless someone else can tell me exactly what is wrong and how to fix it).
iPodNano3
macrumors 6502
Sh3ldon
macrumors regular
Not yet, but I'll definitely try it, thanks. I was thinking about Chromium because I'm convinced that sites are more compatible with Chrome than Firefox, but that's just my impression and could be completely wrong.
You get more privacy with Firefox, and at least Dynasty is kept up to date with the latest official version. Having said that, I do still use C.Legacy which still works for most sites (not all though, Gmail being one that doesn't).
>not all though, Gmail being one that doesn't
What's the failure mode? Can you spoof user agent to an older chrome and see if it starts working? Gmail should in fact work down to chrome 60 or something.
What's the failure mode? Can you spoof user agent to an older chrome and see if it starts working? Gmail should in fact work down to chrome 60 or something.
iPodNano3
macrumors 6502
Firefox hardly uses weird off the wall protocols! But we'd still be using Legacy if the developer hadn't stopped maintaining it.
I hadn't thought of that, maybe I'll try that, but Legacy is now well out of date.
? I haven't experienced any.
iPodNano3
macrumors 6502
i dont know, perhaps this is sorcery. i, and others have reported as well that chromium legacy randomly crashes in the latest versions past v120 when trying to visit a site, or just on the new tab page. another problem, the page sometimes just goes blank while you're actively interacting with the page.
Yes, in Mavericks I experienced blank pages using v121 - however, after switching to Dynasty I discovered there was a final version of Legacy, v124. Pages still go blank briefly in v124, but come back exactly where you were, even if you were in the middle of typing.
Sh3ldon
macrumors regular
True, but what I'm trying to say is that while there are many Firefox-based alternatives for older Macs (Firefox Dynasty and PowerFox, to name a few), as far as Chromium-based browsers go, I think this was the only project (I could be wrong). And it's a real shame the project was abandoned.
I totally agree. However, AFAIK Firefox Dynasty is the only FF project that constantly releases new versions based on the latest FF (the others, such as Arctic Fox for example, are built on old FF versions and designed to load modern pages, whereas Dynasty is the latest FF tweaked to run in older OS's. It's the difference between Lion and later as opposed to Snow Leopard or earlier).
Sh3ldon
macrumors regular
The strange thing is that since Chrome is the most used browser in the world, there isn't a group of people advancing the Chromium open source project, which is not the case with Firefox, precisely. Using Tahoe on my MacBook M1 and with an updated Safari, I had problems with online banking. I downloaded Chrome and everything worked. The problem was definitely not Safari, but rather how the bank's website was built, but it's not the first time I've encountered sites that only work well with Chrome. An open source Chrome would be great.