This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Əgər kömək lazımdırsa lütfən yeni sual verin.

On Firefox 14.0.1, LinkedIn will not display connection contacts after viewing three pages of contacts. This occurs only on Firefox.

  • 2 cavab
  • 2 have this problem
  • 8 views
  • Last reply by bookagent

bookagent
bookagent
more options

Running Macbook Pro, OSX 10.6.8. Only active add-ons are Adbook Plus, Google Disconnect and Stumble Upon. This update has reduced hanging, and has accelerated start-up and speed. This particular issue, however, doesn't occur on any other browser. All Plug-ins are latest versions.

Running Macbook Pro, OSX 10.6.8. Only active add-ons are Adbook Plus, Google Disconnect and Stumble Upon. This update has reduced hanging, and has accelerated start-up and speed. This particular issue, however, doesn't occur on any other browser. All Plug-ins are latest versions.

All Replies (2)

alex_mayorga
alex_mayorga
  • Moderator
more options

I just scrolled over my 200+ connections at http://www.linkedin.com/connections and every entry showed the number of connections they have.

Could you provide exact steps to reproduce the problem, please?

bookagent
bookagent Question owner
more options

Alex -- Many thanks for checking. It appeared that something in my site history may have been the culprit. I'd reinstalled v 14.0.1 once, and the LinkedIn problem remained, then read a post similar to mine. Cleared the day's history -- which would have included the period during which I installed the Firefox update- - and my problem was solved. I didn't suspect the No-Script add-on, because I configured script permissions correctly. So, it was a simple solution. If the problem returns, I will re-post. Thanks for your interest.