We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Wątek został zarchiwizowany. Jeśli potrzebujesz pomocy, zadaj nowe pytanie.

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

  • 2 odpowiedzi
  • 2 osoby mają ten problem
  • 8 wyświetleń
  • Ostatnia odpowiedź od 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.

Wszystkie odpowiedzi (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 Zadający pytanie
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.