Arctic Fox web browser for 10.6 (32 & 64-bit)

[wicknix]

@RobJos : Bummer. Ok, lets try this. Some sites don't like AF's user agent. Chase bank is one of them. Your bank may be similar. Open about:config and create a new useragent override for your bank. Example:
Add new string -> general.useragent.override.yourbank.com and use Mozilla/5.0 (Windows NT 6.3; WOW64; rv:60.9) Gecko/20100101 Firefox/60.9 for the user agent override. See if that fixes it.
Also NY Times loads fine here. Some add-on blocking it maybe? I only use 3 add-ons. ublock, grease monkey, and yes script for what it's worth.

Cheers

 

[RobJos]

@RobJos : Bummer. Ok, lets try this. Some sites don't like AF's user agent. Chase bank is one of them. Your bank may be similar. Open about:config and create a new useragent override for your bank. Example:
Add new string -> general.useragent.override.yourbank.com and use Mozilla/5.0 (Windows NT 6.3; WOW64; rv:60.9) Gecko/20100101 Firefox/60.9 for the user agent override. See if that fixes it.
Also NY Times loads fine here. Some add-on blocking it maybe? I only use 3 add-ons. ublock, grease monkey, and yes script for what it's worth.

Thanks a lot wicknix. I was a bit in doubt that it was related the user agent, but I tried your suggestion — didn't work, unfortunately. If I understood you well the user agent string is not to be entered in about:config, but used as explained now, right?

User agents. A while back because of the Deezer issue I had installed the User Agent Switcher (0.7.3.1) addon, and created, or rather grossly cloned, these user agents:

1. Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:56.0) Gecko/20100101 Firefox/56.0
2. Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:58.0) Gecko/20100101 Firefox/58.0
3. Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36
4. Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; Trident/6.0)

Shortly before I ArcticFox was revealed to me, Deezer had been announcing that they were about to update their site by putting up a floating warning message on accessing the page, saying that my Fx and my other browsers would soon be obsolete. When I started accessing it with AF, that warning went away with the first three user agents above (not no. 4). But that didn't help the fact that Deezer wouldn't play in AF — whereas it was still playing as it always had in Fx 49.5 when they finally upgraded a few weeks ago.

[Btw, your suggestion <Mozilla/5.0 (Windows NT 6.3; WOW64; rv:60.9) Gecko/20100101 Firefox/60.9> doesn't activate playback in Deezer either. The ridiculous thing is that it works perfectly fine in the clumsy interface of VirtualBox/Lubuntu/Fx65.]

Anyway, after this I went on shifting a bit haphazardly between 1, 2 and 3, but lately I have pretty much stuck to 3. — mostly in the vain hope that I would be spared the captcha-hell-by-google. I mean, if Chromium 49 easily takes away the captcha blues, why not Chrome 70? But as said… vain hope.

I don't understand much about how sites interpret this user agent thing (could be that what I concocted there isn't in the correct format), but I also suspect that some sites can detect that they're just that, virtual user agents, not?

Back to the bank, now. I was able to sign in again in Fx 49.5, "only" a question of cookie madness. But after several hours of fuddling about, no amount of cooking or washing away cookies, or turning off ABL, or examining the guts of uBO, or anything else, has got me anywhere in AF.

Here's the sequence, based on signing in Fx 49:

1. launch "https://secure.mybank.com/xxx/x/xxxx/xxxxxxxx/x/login/index"
2. blank page briefly showing a menu in the middle
3. page turns completely blank for a couple of seconds
4. page — with same URL as above — now shows some options for 2-way authentication
5. option selected leads to external site
6. 2WA
7. back again to original site, 2. above
8. page opens on account, same URL still

In AF, the process stops at 3. The page remains completely blank and the progress bar churns forever. I only wish I knew what it is trying to access that it can't, but where to look?

A bit later: if I access the 2WA page at the external site, point 6., it brings me to 7./2., then I'm stuck again on 3.

 

[wicknix]

Unfortunately 2019 and beyond is going to be harsh on browsers not named "chrome" or "edge" (i wont include FF because chrome code is being tossed in to FF as well now too). Anyway, i have 1 last ditch thing you could try. Try a mobile user agent. Most banking sites have mobile apps and/or mobile web pages that don't "require" a big 3 browser. An iPhone UA may just work. Or it may not, but can't hurt to try.
Mozilla/5.0 (iPhone; CPU iPhone OS 10_2_1 like Mac OS X) AppleWebKit/602.4.6 (KHTML, like Gecko) Version/10.0 Mobile/14D27 Safari/602.1

Cheers

 

[madbiker31]

I give up ηMatrix, definitely not for me.

On the other hand, finding a useragent who does not cause a warning interests me even if it means to deceive.

 

[RobJos]

Unfortunately 2019 and beyond is going to be harsh on browsers not named "chrome" or "edge" (i wont include FF because chrome code is being tossed in to FF as well now too). Anyway, i have 1 last ditch thing you could try. Try a mobile user agent. Most banking sites have mobile apps and/or mobile web pages that don't "require" a big 3 browser. An iPhone UA may just work. Or it may not, but can't hurt to try.
Mozilla/5.0 (iPhone; CPU iPhone OS 10_2_1 like Mac OS X) AppleWebKit/602.4.6 (KHTML, like Gecko) Version/10.0 Mobile/14D27 Safari/602.1

Thanks again, wicknix, I will certainly add this one to my growing “collection” of UA, but before I test it, here's what my dreams have advised me to test as soon as I got up today. I'd say that the result seems to point to the UA not being related to this particular problem.

I went back to this suggestion of yours and re-opened the profile created for testing purposes. For other users: a “naked” profile with no addons, all plugins deactivated and that only presents the ArcticFox UA. Guess what? No problem whatsoever opening this bank's login page!

Then, paying more attention to your mention of the addons you use (yesterday was a bit overwhelming, on all fronts), it seemed obvious that an addon was the underlying cause of this particular hassle. So for the first time I made use of the Extension Conflict Troubleshooter addon, which works in the same smart way as Conflict Catcher of bygone days (for those hags and hogs old enough like me to remember Mac OS9). It seemed obvious… but it wadn't, at least using it in the way one is supposed to: which is by selecting one “suspicious” addon before starting a diagnostic session. As I couldn't suspect any particular addon, I tried starting two sessions with two different ones, one that affects much of the browser's interface, the other a relatively inocuous one, but it didn't make no difference.

This could bring us back to the reason you had me create a new profile in the first place — favicons not showing in the Bookmarks and History. This issue was permanently fixed by deleting certain files in the profile that had been imported from Firefox, which forced ArcticFox to automatically re-create them. Now, following this line of thought, which one of the following files (list taken from the test profile) would you suggest that I either delete (and have it re-created automatically) or copy over from the test profile — without this procedure affecting my working profile?

blocklist.xml
cert8.db
compatibility.ini
content-prefs.sqlite
cookies.sqlite [NOTE: I have erased repeatedly all cookies related to that bank]
extensions.ini
extensions.json
formhistory.sqlite [NOTE: Form History has been deleted several times]
key3.db
localstore.rdf
mimeTypes.rdf
permissions.sqlite
pluginreg.dat [NOTE: list of plugins in test profile is much shorter than that in working profile — and Firefox]
prefs.js
search.json
secmod.db
sessionCheckpoints.json
sessionstore.bak
sessionstore.js
SiteSecurityServiceState.txt
times.json
webappsstore.sqlite
xulstore.json

I'm open to any other idea, of course. Just keep in mind that Fx49, which presents its own UA, opens the bank's login page without problem.

Take care,
[doublepost=1553621146][/doublepost]While at it, figuring out a couple of other things.

Using that same Extension Conflict Troubleshooter to try and fix the Title Bar not showing at launch and having to go through some gymnastics to get it to appear (pt.1) didn't get me anywhere either. No addon is apparently responsible for this behaviour. There's a bit of more of a drawback here: if the page you're on when you do this toggling of keyboard shortcuts is a login page, it forces you to login again. A drag especially on Amazon, which of late has started to use some captcha stuff of their own more or less at each login.

Else, a link followed this morning was giving me a page that was quite readable to begin with, but suddenly turned completely blank while I was scrolling down. Blocked the scripts, refreshed the page, and here it was, readable and stable to the end. Applied the same idea, blocked scripts on the New York Times, and got the contents right away. So that's taken care of. Probably will get used many times in the future.

Also found that I cannot drag a Private Window by grabbing its (Non-)Title Bar. One has to grab it somewhere else in order to move it around.
[doublepost=1553621984][/doublepost]

(...) finding a useragent who does not cause a warning interests me even if it means to deceive.

Is there anything wrong with those suggested here and here?

 

[wicknix]

Yeah, i need to work on fixing private window controls again. I had it working in early releases, but it broke the ability to enable devtools. People wanted devtools (the web developer portion of the tools menu), so i "broke" private window mode to get them back.

Now, for the profile.... Hard to say. I would make a zip file of your profile first. That way you can always put a good copy back if something doesn't work out. xulstore.json isn't important. It just remembers your browser window position on screen and the size it was before the browser was closed. I would leave the extensions.ini and extensions.json alone though, the rest you could probably safely copy over. I would probably do 1 file at a time, start the browser, and test, and repeat process until you get your desired results. Or go balls to the wall and copy them all over (minus extensions files) and hope for the best. Either way, you created a zip archive of your original profile if it fails.

Cheers

 

[madbiker31]

Is there anything wrong with those suggested here and here?

Yes, on the about:config page there are ten different useragent (google things, netflix, yahoo, etc.).

Where and how to access the good way to modify the general useragent of ArcticFox received by the websites ?

Edit : I think i found a way by reading again this post and https://forum.palemoon.org/viewtopic.php?t=17887
I have to create a new string general.useragent.override.mysite.com for every sites that disturb me.
Next performance is to find the good string value, Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:56.0) Gecko/20100101 Firefox/56.0 for example.

 

[RobJos]

Now, for the profile.... Hard to say. I would make a zip file of your profile first. That way you can always put a good copy back if something doesn't work out. xulstore.json isn't important. It just remembers your browser window position on screen and the size it was before the browser was closed. I would leave the extensions.ini and extensions.json alone though, the rest you could probably safely copy over. I would probably do 1 file at a time, start the browser, and test, and repeat process until you get your desired results. Or go balls to the wall and copy them all over (minus extensions files) and hope for the best. Either way, you created a zip archive of your original profile if it fails.

You won't believe this…

I had already gone through ⅔ of those files, painstakingly replacing them 1 by 1, collecting and thinking of mailing you the sources of the bad and the good pages, basically getting sick of it all, when the God of Small User Agents spake to me. I simply reverted to AF's Default User Agent (you may remember that when you suggested a new UA, I was already set with another one than the default).

And yes, that login page showed up immediately. I only can hope that after dozens of attempts the bank's security people won't ban anything that looks like AF ;-(

Now, what does this teach us, besides telling us that your Arctic Critter is even better than you knew? I'd like to hear your thoughts on this…

[“Balls to the walls“, huh? Where's this one from? Just my cultural curiosity…]

Btw., not understanding how this kind of thing can happen: is it OK now to remove the strings you had me enter in about:config?
[doublepost=1553716398][/doublepost]So, while this evening is happily rolling, kindly allow me to plague you with two (hopefully) small things:

- in both 1. my working profile and 2. the test profile there's a 0 Kb file called SiteSecurityServiceState.txt. In 1., the modified date goes back to last year some time, meaning that it came with Firefox Firefox. It never changes. In 2, on the other hand, the modified date gets updated each time I launch and quit this profile. Does this have any relevance to anything?

- The Downloads: Show in Window, Tab, or Sidebar 1.4.0 addon lets you choose between showing downloads in a New Window, a New Tab or the Sidebar. I'm using this last one. There's a small hassle, though: each time I download something the Sidebar opens automatically, whereas I'd rather open it when it suits me (changes the format of the main page, not always desirable). Moreover, if a download has taken place during the current session, any New Window opened afterwards shows up with the Sidebar/Downloads open. Is there any true/false something that can be edited in about:config to make it stop that?

Anticipated thanks...

 

[wicknix]

Glad you sorted it out. I use the Native UA myself. If i run in to an anal site i just add a FF UA in about config. 95% of the time is just bad site admins only wanting to support 3 browsers, when the other 15 or so browsers can easily handle the site fine. Sadly, that's just the way it is. Yeah you can "reset" any strings you manually entered in about:config safely.

As for balls to the wall, it's something my buddy and i always say. It stemmed from this song back in our high school days.

Edit: The security.txt probably isn't a big deal. You could probably copy the updated one over. Your FF one is probably "locked" which is why it wont update. For your downloads add-on, i'd check about:config. There might be an option. I don't know where to look however since i dont have it installed. Sometimes you'll find it under the devs real name, sometimes the app name, or sometimes just randomly tossed in various spots.

Cheers

 

[swamprock]

Glad you sorted it out. I use the Native UA myself. If i run in to an anal site i just add a FF UA in about config. 95% of the time is just bad site admins only wanting to support 3 browsers, when the other 15 or so browsers can easily handle the site fine. Sadly, that's just the way it is. Yeah you can "reset" any strings you manually entered in about:config safely.

As for balls to the wall, it's something my buddy and i always say. It stemmed from this song back in our high school days.

Edit: The security.txt probably isn't a big deal. You could probably copy the updated one over. Your FF one is probably "locked" which is why it wont update. For your downloads add-on, i'd check about:config. There might be an option. I don't know where to look however since i dont have it installed. Sometimes you'll find it under the devs real name, sometimes the app name, or sometimes just randomly tossed in various spots.

Cheers

"Let's plug a bomb in everyone's ass..."

 

[z970]

"Let's plug a bomb in everyone's ass..."

That's certainly an acquired taste of music...

 

[RobJos]

Glad you sorted it out. I use the Native UA myself. If i run in to an anal site i just add a FF UA in about config. 95% of the time is just bad site admins only wanting to support 3 browsers, when the other 15 or so browsers can easily handle the site fine. Sadly, that's just the way it is. Yeah you can "reset" any strings you manually entered in about:config safely.

Actually, having no experience with editing strings in about:config I hadn't understood your instructions properly (thought that “general.useragent.override.xxxx.com" was meant to be the value, and made a new entry "Mozilla/5.0 etc.” in User Agent Switcher). Thanks to the link passed by madbiker, I could create a couple of them strings correctly.

As for balls to the wall, it's something my buddy and i always say. It stemmed from this song back in our high school days.

Ah! Unsuspected sonorities from past centuries… The shift from late seventies acid to early eighties acid still amazes me. And so does that pain in the YouTube, wouldn't let me access it "from my country", even after I had switched to a server in the US. Heard it from another video, anyway.

For your downloads add-on, i'd check about:config. There might be an option. I don't know where to look however since i dont have it installed. Sometimes you'll find it under the devs real name, sometimes the app name, or sometimes just randomly tossed in various spots.

I hadn't realised that it wasn't a function specific to the browser. A zillion strings with "sidebar", half-a-zillion with "download", but reasonably fewer "downloads" later, I found out by disabling the addon that its string was:

extensions.sidebarslist.lastURI; Value: chrome://browser/content/history/history-panel.xul

And what did I make out of this cryptic stuff? Only spending enough time on such a life-and-death issue to teach me me that I can very well live a happy life without the Downloads in the Sidebar. Spoiled by years of AIOS (All-In-One-Sidebar), that's what it was.

And I have to once again admit heartily that your warnings against importing a profile from Firefox are correct. I found plenty of strings in about:config that were related to long gone Firefox extensions, like AIOS mentioned above. Impossible to get rid of them all, even those that are easy to figure out.

The security.txt probably isn't a big deal. You could probably copy the updated one over. Your FF one is probably "locked" which is why it won't update.

Correct, the "new" one is getting refreshed regularly. I see now that the old one wasn't locked the way it usually is in the Mac OS's Finder, but all of its permissions were set to Read only, I wouldn't know why. I should probably go and check the permissions of the rest of the profile.

 

[z970]

And so does that pain in the YouTube, wouldn't let me access it "from my country", even after I had switched to a server in the US.

I smell Article 13.

The EU has killed the Internet for those in Europe, due to "copyright" reasons, and other garbage.

In any case, @wicknix, Arctic Fox .16 comes out with the jemalloc Segmentation Fault on Debian Sid ppc64 in a 32 bit userland. This one is not a contributed build and was the 32 bit version (G3/G4/G5) offered on GitHub. Surely, this Debian 9 / Ubuntu 16 version must also work for Sid, as 9 was never released for PPC, and the same .15 release worked fine before.

This is a very common issue. Solutions appreciated.

 

[RobJos]

I smell Article 13.

The EU has killed the Internet for those in Europe, due to "copyright" reasons, and other garbage.

I know exactly what you're talking about, the majority of degenerates at the EU parliament has just passed it yesterday. But in this case with YouTube, I've seen it happen before, not very often as I rarely have any communication with people in the US.

 

[wicknix]

as 9 was never released for PPC

You sure about that? https://cdimage.debian.org/cdimage/ports/9.0/powerpc/iso-cd/
I build my releases the same every time. I'm pretty sure you last used a contributed build if you keep getting the jemalloc errors. I don't disable that. The Amiga / older ubuntu builds have it disabled. I'd try one of xeno74's builds. Sid is by no means debian 9. As a rolling test bed, Sid is really just a mutt.

Cheers

 

[z970]

You sure about that? https://cdimage.debian.org/cdimage/ports/9.0/powerpc/iso-cd/
I build my releases the same every time. I'm pretty sure you last used a contributed build if you keep getting the jemalloc errors. I don't disable that. The Amiga / older ubuntu builds have it disabled. I'd try one of xeno74's builds. Sid is by no means debian 9. As a rolling test bed, Sid is really just a mutt.

Cheers

You know what I mean... My point was that more people (in our circle of interest) are using Sid as opposed to Stretch.

Sid's a damn fine mutt.

 

[CooperBox]

Currently completely renovating a MacBook3,1 for a friend, it's running OS 10.6.8, and I've just installed Arctic Fox. It's so rapid that I'm simply amazed, YTube running a treat etc. Thanks again to Wicknix for his great efforts!

 

[swamprock]

Thanks a lot wicknix. I was a bit in doubt that it was related the user agent, but I tried your suggestion — didn't work, unfortunately. If I understood you well the user agent string is not to be entered in about:config, but used as explained now, right?

User agents. A while back because of the Deezer issue I had installed the User Agent Switcher (0.7.3.1) addon, and created, or rather grossly cloned, these user agents:

1. Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:56.0) Gecko/20100101 Firefox/56.0
2. Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:58.0) Gecko/20100101 Firefox/58.0
3. Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36
4. Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; Trident/6.0)

Shortly before I ArcticFox was revealed to me, Deezer had been announcing that they were about to update their site by putting up a floating warning message on accessing the page, saying that my Fx and my other browsers would soon be obsolete. When I started accessing it with AF, that warning went away with the first three user agents above (not no. 4). But that didn't help the fact that Deezer wouldn't play in AF — whereas it was still playing as it always had in Fx 49.5 when they finally upgraded a few weeks ago.

[Btw, your suggestion <Mozilla/5.0 (Windows NT 6.3; WOW64; rv:60.9) Gecko/20100101 Firefox/60.9> doesn't activate playback in Deezer either. The ridiculous thing is that it works perfectly fine in the clumsy interface of VirtualBox/Lubuntu/Fx65.]

Anyway, after this I went on shifting a bit haphazardly between 1, 2 and 3, but lately I have pretty much stuck to 3. — mostly in the vain hope that I would be spared the captcha-hell-by-google. I mean, if Chromium 49 easily takes away the captcha blues, why not Chrome 70? But as said… vain hope.

I don't understand much about how sites interpret this user agent thing (could be that what I concocted there isn't in the correct format), but I also suspect that some sites can detect that they're just that, virtual user agents, not?

Back to the bank, now. I was able to sign in again in Fx 49.5, "only" a question of cookie madness. But after several hours of fuddling about, no amount of cooking or washing away cookies, or turning off ABL, or examining the guts of uBO, or anything else, has got me anywhere in AF.

Here's the sequence, based on signing in Fx 49:

1. launch "https://secure.mybank.com/xxx/x/xxxx/xxxxxxxx/x/login/index"
2. blank page briefly showing a menu in the middle
3. page turns completely blank for a couple of seconds
4. page — with same URL as above — now shows some options for 2-way authentication
5. option selected leads to external site
6. 2WA
7. back again to original site, 2. above
8. page opens on account, same URL still

In AF, the process stops at 3. The page remains completely blank and the progress bar churns forever. I only wish I knew what it is trying to access that it can't, but where to look?

A bit later: if I access the 2WA page at the external site, point 6., it brings me to 7./2., then I'm stuck again on 3.

Google's captchas are a nightmare, especially with a VPN... so much so, I stopped using Google for searches.

 

[RobJos]

Google's captchas are a nightmare, especially with a VPN... so much so, I stopped using Google for searches.

The problem is not Google as such (been using DuckDuckGo for ages, and more recently Startpage, Ecosia and MetaGer, which for that matter has a very nice declaration of intent, so there's plenty of alternatives out there). Rather it's all the site owners that let Google brainwash them into stuffing their code with Google scripts and into paying it for the privilege of using its captcha thing and the right to collect as much information as possible about every single one of our movements. Most sites you complain to only BS you back telling you that it's "for your protection". But maybe something is about to change: recently a site owner admitted to me that things had become unbearable, but that he didn't know what else he could use in order to counter attacks on his site.

 

[RobJos]

Questions, requests and even… thoughts for wicknix and others interested.
No rush, but please don't forget the relevant number with your replies.

1. Is there an elegant way to disable keyboard shortcuts? Specifically +⇧+F, which I never need but always seem to hit at the wrong moment (call it senility…). If about:config is the right place, there are too many "fullscreen" entries there for me to be able to figure it out.

2. HTTPS Everywhere: https-everywhere-5.2.21.xpi installs fine, so there doesn't seem to be any incompatibility here. But if I try to change any one of the three settings in the prefs, they are back to default as soon as I close and re-open the panel. This is also the case when I install this add-on in a new, “naked” profile.

3. With regard to the Title Bar not showing at launch (and requiring Opt/Alt+Ctl+T pressed twice to get it to turn up in any normal window, I came across this at the repository of the Private Tab addon (at the bottom):

"Correctly handle first browser window in Firefox 60+ (browser.startup.blankWindow = true)". The discussion after that is in Russian, so I'm twice handicapped, but the string "browser.startup.blankWindow" is not to be found in about:config. Would my AF explode if I created it? Apologies if my ignorance causes any confusion.

Btw., the Title Bar always appears right away in a new Private Window.

4. My installation of the FlashGot add-on in Firefox used the Download Manager DTA Turbo. Here in AF, in the midst of a plethora of greyed-out entries, only three can be selected: Browser Built In, cURL and pyLoad. What does it mean, and which one is to be preferred?

5. On one particular site the Scroll Bar to the right disappears almost right away. This does not happen in other browsers. Can it be fixed, or is there a workaround? I have the NewScrollbars (aka NoiaScrollbars) add-on installed, but so far this is the only site with this bug.

6. Kudos for introducing something I've often missed in Firefox: the Containing Folder and Containing Folder Path columns in the Bookmarks library.

7. It seems that since installing AF my wireless mice occasionally (like a couple of times a day) hiccup or even slow down to a crawl — under normal conditions a sign that the batteries are in need of being charged. Plural, as this happens on two different machines (and of course two different mice). Has anyone else experienced this?

8. In the Add-ons Manager, some entries have a blue dot behind them, others an orange one. What are they supposed to indicate?

9. Cosmetics: usually, when I open ArcticFox's preferences, I get this:

instead of this (normal):

- which I only get after closing and re-opening the preferences.

10. Flash vs. HTML5. I had kind of understood that HTML5 was a better protocol, but never paid much attention to it as there were plenty of sites in Fx49 that required Flash. Occasionally Fx would block the plugin when it was outdated, upon which I'd go and get an update at Adobe's. Here in AF, I have Flash set to “Ask to Activate”, but it never has asked in two months, not even once. Does this mean that AF only uses HTML5 and that Flash can safely be set to "Never Activate"? Which would have the added advantage that this setting is generally considered as preferable as far as anonymous browsing goes.

If so, if someday a site doesn't work properly, how do I know that it's because it's needing Flash? And if HTML5 is better (for whatever reason), what's the point of the HTML5 Media Tuner addon that disables it?

The link to YouTube there shows that "MSE & WebM VP9" is not supported in AF — which seems to correlate with Enable MSE for WebM video being greyed-out in the Content pane of AF's preferences. A feature that's waiting to be implemented? Not that I'm running after it, it's just that I'd like to understand.

11. The Werewolf add-on interferes with Tab Mix Plus. Removed.

12. Thank you for reading this far, and enjoy what's left of this Sunday.

Robert

 

[wicknix]

I'll take a stab at a few. Most your oddities are a result of you importing of a full FF profile, but you already know that.
2) That's not always the case. Just because an extension installs fine without an error message doesn't mean it will work, or work properly. This is the case with numerous FF add-ons. I'd just chalk up https-everywhere as not working.
8) Blue dot means PM/AF compatible with support from the developer. Orange dot means it's meant for FF and the developer doesn't offer support for PM/AF. If an orange dot add-on works, that's great, but if it doesn't, it probably never will.
10) Correct. Only VP8 is supported in AF currently. I have been trying to back port VP9 code in to AF, but so far i haven't had much luck.

Cheers

 

[madbiker31]

The main problem I have with ArcticFox is with Google Maps and Street View.

The first display of the place I chose is OK, I can moove one or two times, then impossible to moove my position in any direction.

For information NewMoon 27.9.4 has the same behaviour.

What can I do to progress ?

In that case I switch to Firefox 45.9 ESR or 48.0.2 (last available), Safari 5.1.10 is refused by Google Maps...

 

[snowy moon]

2. HTTPS Everywhere: https-everywhere-5.2.21.xpi installs fine, so there doesn't seem to be any incompatibility here. But if I try to change any one of the three settings in the prefs, they are back to default as soon as I close and re-open the panel. This is also the case when I install this add-on in a new, “naked” profile.

HTTPS Everywhere is one of these add-ons that needs to be installed via Moon Tester Tool. So you uninstall your HTTPS Everywhere first, then install Moon Tester Tool, go to about:addons > Moon Tester Tool, from there you can select the file for https-everywhere-5.2.21.xpi from your harddrive, which then will be installed.

Here is an archived page with a nice overview about add-on versions, and which of them need to be installed with Moon Tester Tool. That page is outdated for recent versions of PM, but is of course still relevant for us Arctic Fox users:
https://web.archive.org/web/20180706043049/https://addons.palemoon.org/incompatible/

 

[RobJos]

HTTPS Everywhere is one of these add-ons that needs to be installed via Moon Tester Tool. So you uninstall your HTTPS Everywhere first, then install Moon Tester Tool, go to about:addons > Moon Tester Tool, from there you can select the file for https-everywhere-5.2.21.xpi from your harddrive, which then will be installed.

Here is an archived page with a nice overview about add-on versions, and which of them need to be installed with Moon Tester Tool. That page is outdated for recent versions of PM, but is of course still relevant for us Arctic Fox users:
https://web.archive.org/web/20180706043049/https://addons.palemoon.org/incompatible/

Cool, many thanks indeed! I must have skipped this one when I went through the Pale Moon addons, likely after reading that “Moon Tester Tool is intended for advanced users and for test purposes only!”. HTTPS Everywhere is now happy here. It's probably going to take a few days to go through that page on Archive.org, but if you (or anyone else) know of some of those addons defined as incompatible that are definitely badly incompatible with AF 27.9.16, please let us know.

 

[mrkapqa]

Hello , i am late to the party here.

Is there already a version for OSX 10.5 Leopard or rather not?


Thanks, on Snow Leopard it is really fast browser, only it seems struggling with Google Drive.

Looking forward using it extensively.