Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Avatar for Username

Caută ajutor

Atenție la excrocheriile de asistență. Noi nu îți vom cere niciodată să suni sau să trimiți vreun SMS la vreun număr de telefon sau să dai informații personale. Te rugăm să raportezi activitățile suspecte folosind opțiunea „Raportează un abuz”.

Află mai multe

Firul de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

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

  • 2 răspunsuri
  • 2 au această problemă
  • 4 vizualizări
  • Ultimul răspuns dat de 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.

Toate răspunsurile (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 Deținătorul întrebării
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.