No links display in PM 7.01?

Users and developers helping users with generic and technical Pale Moon issues on all operating systems.

Moderator: trava90

Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
ubersurfer

No links display in PM 7.01?

Post by ubersurfer » 2011-10-08, 00:14

I no longer see links in pop-up/status bar/address bar when I hover them in PM 7.01. Anyone else?
:wtf:

User avatar
satrow
Forum staff
Forum staff
Posts: 1940
Joined: 2011-09-08, 11:27

Re: No links display in PM 7.01?

Post by satrow » 2011-10-08, 17:00

It's working as it should here.

You've checked that the status bar add-on is enabled and that the options are for it are correctly set (including in the main PM View > Toolbars > Status Bar)?

Have you recently installed a new add-on?

User avatar
Night Wing
Knows the dark side
Knows the dark side
Posts: 5846
Joined: 2011-10-03, 10:19
Location: Piney Woods of Southeast Texas, USA

Re: No links display in PM 7.01?

Post by Night Wing » 2011-10-08, 18:06

Working properly for me.
MX Linux 25.1 (Infinity) Xfce w/Pale Moon, Waterfox, Firefox
Linux Debian 13.4 (Trixie) Xfce w/Pale Moon, Waterfox, Firefox

User avatar
Moonchild
Project founder
Project founder
Posts: 39110
Joined: 2011-08-28, 17:27
Location: Sweden

Re: No links display in PM 7.01?

Post by Moonchild » 2011-10-09, 17:30

"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

ubersurfer

Re: No links display in PM 7.01?

Post by ubersurfer » 2011-10-09, 23:50

Thanks so much, guys.

Taking the tips you provided, I dug deeper, did a complete reinstall and reconfig and, now, all is well. I guess the original issue was caused by a rogue setting somewhere.