Este site está com funcionalidades limitadas enquanto realizamos manutenção para melhorar sua experiência de uso. Se nenhum artigo resolver seu problema e você quiser fazer uma pergunta, nossa comunidade de suporte pode te ajudar em @FirefoxSupport no Twitter e /r/firefox no Reddit.

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

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

  • 2 respostas
  • 2 têm este problema
  • 8 visualizações
  • Última resposta de 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.

Todas as respostas (2)

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?

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.