Forum adverts like this one are shown to any user who is not logged in. Join us by filling out a tiny 3 field form and you will get your own, free, dakka user account which gives a good range of benefits to you: No adverts like this in the forums anymore. Times and dates in your local timezone. Full tracking of what you have read so you can skip to your first unread post, easily see what has changed since you last logged in, and easily see what is new at a glance. Email notifications for threads you want to watch closely. Being a part of the oldest wargaming community on the net. If you are already a member then feel free to login now.

On my PC, running firefox, for some reason the Dakka Speech yellow highlights aren't working anymore. I mouse over them, and nothing happens. Help? Sometimes I dont know what people is talking about. (lack of grammar used for entertainment)

firefox has some glitches with it when firefox gets bugged out. Making sure that firefox is not using custom style sheets to override ours is the first thing to check, making sure noscript is not installed (or similar) is next, and if you are really troubled by it, a manual install of firefox has been known to fix the problem in the past.

Alright, thanks. 90% sure it's my ad-blocker. Probably because of those stupid pop-up "phrase" ads that some sites have.

It's not an adblocker issue. The problem is tt_Tip function has a return statement in it if the var mobilemode is true.

Viewing it on Chrome 17, mobilemode is actually set to true.

Ronin-Sage wrote:It's not an adblocker issue. The problem is tt_Tip function has a return statement in it if the var mobilemode is true.

Viewing it on Chrome 17, mobilemode is actually set to true.

How would I fix it?

RavienCoromana wrote:

Ronin-Sage wrote:It's not an adblocker issue. The problem is tt_Tip function has a return statement in it if the var mobilemode is true.

Viewing it on Chrome 17, mobilemode is actually set to true.

How would I fix it?

It's a problem for the forum maintainers to fix. I'm safely assuming mobilemode is only set to true if the user is on a mobile device, but it's being set to true on Chrome on Windows 7, so obviously something isn't right.

You can temporarily fix it for yourself by opening your browser's javascript console and setting mobilemode to true and false and observe the effects(apparently the glossary is set to not function when mobilemode is true).

There are known firefox issues, and adblocker is a possible blocker as well.

kudos for digging through the ugly javascript (combined from 4 sources and yet to be cleaned up!) Mobilemode is set in the obfuscated/compressed header on each page and is not exclusive to using a mobile device but is in fact part of a range of automatic (as well as prompted) system detection code.

It is possible that the OP is using the mobile theme (or print friendly) which use the mobilemode flag, so OP, try updating your theme to be the default dakka theme (use the switch theme link on any page). If that does not fix it then it is almost certainly an issue with your browser configuration.

Confirmed that mobile theme is the cause(tested on Chrome 17)

Heh, I actually had my own preferences set to use the mobile theme, which is how/why I came upon this thread, because I saw it had 'lite' or something in the theme name so I was like "ooo lightweight elegance".