@WinterClaws Can you do me a favor? Try this. Change the status bar to show "pop-ups" instead. It's basically like having a hidden status bar until you hover links. That is the setting i use (to have more screen space). That should work. In the meantime i'll look in to what might be randomly causing that. (tools -> status bar prefs -> status -> general -> show links in pop-up).
Cheers
Sure. Thanks for the suggestion. But it didn't seem to work. The nice thing about beta-testing-type stuff is that it makes one aware of options they didn't know about (like that status bar prefs thing).
Anyway I could totally live with that popup behavior as you describe, and tried various bits of options within that dialog box (like Hide Status after x seconds) but...no joy. Still not showing any links. As a simple example,
http://addons.palemoon.org doesn't show links when hovering on the menu bar on top, but does so on Safari. Am encountering similar with other sites (including https)...
[doublepost=1541594471][/doublepost]That reminded me...maybe I should pass on a couple of personal suggestions to new users of this browser that I think might be useful (and to avoid learning the hard way).
- First is the default option not to track history (ArcticFox/Prefs/Privacy/Tracking). That sounds good in theory, until you find out that it also means that the browser will never remember its previous links/tabs/sessions. If that means more to you than the privacy concerns (as I've decided, after losing one too many sets of important windows open after an AF crash...painful
) then you might want to set it to "Remember History" as I have. That will also allow things like restoring closed tabs and such (another feature my trigger-finger browsing habits can greatly appreciate).
- And as an adjunct of the above suggestion, it also allows for showing windows and tabs from last time. You can set that in the General tab of Preferences. Those who wanted to turn that option on but were befuddled why it was greyed out, well...that's the reason.
- And finally, my personal loathing of Java aside, that add-on has also been the cause of a couple of AF crashes for me. So, I feel justified to also suggest setting the Java Applet Plug-In to "Ask to Activate" (or "Never Activate" altogether). That is in Tools/Add-ons/Plugins. At least that way you have forewarning when a page has some java content that will try to activate it, and can judge if it is worth any possible crash or security risk to activate or not. Actually I'm a big fan of setting pretty much any plugin to manually ask before activating (learned the hard way on Chrome years prior), so I respectfully suggest that this might be best set as default in future compiles/versions of the browser too.
