I don't want to sound ungrateful och put down wicknix efforts, but why not try to make one really good browser instead for having it split up in Arctic Fox, Interweb and Spiderweb?
I went through and found my old archived AF compatible extensions and themes. They are now uploaded. Hopefully they still work with current AF releases.
Cheers
That's where i uploaded them. Hopefully Riccardo will find a better permanent home for them at some point.
I actually get this with Chromium-Legacy every time i update to a new version on 10.7. I never really looked in to it personally. Figured that's just how a browser works. As for the ever changing web, i've been saying for the last few years that a linux or windows 7 (or above) VM would be needed to access g00gle-ified websites on 10.6. Sadly that's just what the web is becoming. Web pages are no longer simple html and basic javascript, but rather applications wrapped up to work in a modern browser.A little detail: when launching v.40 the first time with an active profile, on my system at least, the System Preferences' Security/Firewall/Advanced requests it to Accept incoming connections. This is the first time I see this happening in the case not only of AF, but of any browser.
I'm sorry, @wicknix, really sorry after all the work you and your colleague have done for us, but one Saturday evening, one whole Sunday and a good chunk of Monday's dawn hours later, I'm giving up on v.40. After all that time there were still some issues (see below) that couldn't get resolved without dedicating them even more time, so instead I went and checked a bunch of the sites that had forced me in the first place to move over to SpiderWeb, then to Linux/Firefox and PaleMoon: banks, exchanges, webmails, IT providers and others (for example Trustpilot.com, or sites that make use of parastorage.com javascripts). Every single one of them gave me a dreaded variant of that “Browser not supported”, or just a blank page.
Staying on ancient OS's means we have to pick our battles, and sadly, our battle is with the modern web these days.I actually get this with Chromium-Legacy every time i update to a new version on 10.7. I never really looked in to it personally. Figured that's just how a browser works. As for the ever changing web, i've been saying for the last few years that a linux or windows 7 (or above) VM would be needed to access g00gle-ified websites on 10.6. Sadly that's just what the web is becoming. Web pages are no longer simple html and basic javascript, but rather applications wrapped up to work in a modern browser.
As for AF, i haven't touched an ounce of code in it for about 2 years now. I have no idea whats been added or removed. I do know he has been adding support for more obscure operating systems like NetBSD, OpenBSD, FreeBSD on various platforms like arm and mips because they really lack any decent web browsers. In doing so it *may* be hampering 10.6 compatibility (as noted with crashes since the end of the v27 era), but i can't be certain of that.
Honestly, InterWeb is the most compliant snow leopard browser, even if it is slowly falling behind by modern standards. It's still the best of the bunch (AF, IW, SW, TenFourFox, and FF-Legacy/Nightly). Neither AF or Nightly support TLS 1.3 for instance. IW has push notifications (works great for this forum if enabled btw), and in my opinion should be considered and recommended as the only 10.6 browser. AF's code base is just now only at FF40 levels, which is even older than TFF at 45.9. Nightly is at 52.9 and hasn't been updated in 2 years, while IW/SW are at 52.9-60.9 and receive minimal, but major, updates. Still old by todays standards, but not as old.
Staying on ancient OS's means we have to pick our battles, and sadly, our battle is with the modern web these days.
Cheers
Not sure how what I wrote could be interpreted that way, but wicknix pretty well knows what I think of him and his work, and that's what counts, IMHO.This isn’t the fault or due to the intervention of @wicknix ’s efforts in maintaining AF. It’s not helpful to put him, a volunteer, on the spot like this.
[...] this isn’t the doing of wicknix, and there’s not a lot he can do here.
Not sure how what I wrote could be interpreted that way, but wicknix pretty well knows what I think of him and his work, and that's what counts, IMHO.
No. Legacy is current chromium (currently at 106) back ported to 10.7 - 10.10. Sadly 10.6 support isnt possible. I've seen whats required to have any hope of it on 10.6 and understand why.Chromium: mine is v.49 from 04.16 (is that the same as your “Legacy”?)
Its fine. We've PM'd a lot over the years. Sometimes typed text doesn't come across as it would if it were spoken, and it gets misinterpreted. No harm, no foul.Your remarks to him were probably better suited for a private message
No. Legacy is current chromium (currently at 106) back ported to 10.7 - 10.10. Sadly 10.6 support isnt possible. I've seen whats required to have any hope of it on 10.6 and understand why.
Its fine. We've PM'd a lot over the years. Sometimes typed text doesn't come across as it would if it were spoken, and it gets misinterpreted. No harm, no foul.
So, 64 bit AF 40.0 works again on SL, thanks wicknix and @rmottola.64-bit AF is up. Please test it.
Here's the work-a-round link to bypass the spinning wheel of death on github.
All in all, a nice snappy browser, no dramatic problems, important add-ons like uBo and uMatrix do work, others too. Although I prefer SpiderWeb and Tenfourfox, InterWeb..., but it is nice to have a fast little browser seperately to do quick searches, read stuff.
Versions I use are latest from here uBo-for-firefox-legacy and ηMatrix. If they don't show up in navigation bar, go to Menu > View > Toolbars > Customise... a dialog rolls down with gui items and add-on icons, uBlock and uMatrix should be there, drag them to where you want them.I was having trouble accessing uBlock and uMatrix on AF 40, despite bringing over my legacy add-ons from another vintage Mozilla browser — namely, neither icon appearing on the location bar level and no readily apparent way to access their settings. Where should I be looking for access and configuration for both of these — or, would it be wiser to locate versions of both which were optimized originally for Palemoon? Cheers.
Ok, after editing it's install.rdf, Xmoon theme works in AF 40. And it circumvents the non-matching toolbar-icons.Xmoon theme got disabled, but standard theme is nice enough and slim, if used with small icons.
Here's the large list that's missing.frameworks simply absent
Here's the large list that's missing.