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

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

I can no longer navigate to or interact with SharePoint libraries since upgrading to 61.0.2 (64-bit) on my MacBook Pro.

  • 3 件の返信
  • 1 人がこの問題に困っています
  • 3 回表示
  • 最後の返信者: Gerd

Meagen
Meagen
more options

Since upgrading to 61.0.2 (64-bit) on my MacBook Pro running OS X El Capitan version 10.11.6, I can login and navigate to the required SharePoint sites within Office365 however once the SharePoint site is displayed I cannot see the folders or naviaget within each site library. Sorry, can't provide screenshots as SharePoint is work related.

Since upgrading to 61.0.2 (64-bit) on my MacBook Pro running OS X El Capitan version 10.11.6, I can login and navigate to the required SharePoint sites within Office365 however once the SharePoint site is displayed I cannot see the folders or naviaget within each site library. Sorry, can't provide screenshots as SharePoint is work related.

すべての返信 (3)

WestEnd
WestEnd
more options

In this instance SharePoint works best with IE as they are better integrated software for privacy and security reasons. FF has not been SharePoint friendly that I know of. Even at work I use SharePoint from IE because of the software integrations. So you should contact Office 365 on what more options you can do.

Meagen
Meagen 質問者
more options

Until the upgrade last week SharePoint worked fine. I would prefer to continue using FireFox for a number of reasons. Thank you for the pointer.

Gerd
Gerd
more options

I was able to fix my issues with Sharepoint by completely deleting all cookies and website data on all MS domains inside of FF. Can you try that as well?

If it doesn't work, a full browser refresh (reset) might also be a solution.