SharePoint / SharePoint/sp-dev-docs

Spfx webparts running in safari

Open
#9,795 5 comments 0 reactions 1 assignee View on GitHub

@Ashlesha-MSFT is already working on this.

Since Jun 19, 2025.

Needs: Triage :mag: sharepoint-developer-support type:bug-confirmed type:bug-suspected
Dominant language
PowerShell
Stars
1.4k
Forks
1.1k
Avg merge
4d 12h
Merged PRs (30d)
12

Description

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

macOS

What browser(s) / client(s) have you tested
  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)
Additional environment details

macOS 14.5
safari 17.5
chrome v126
spfx 1.19

Describe the bug / error

I have developed an spfx webpart for use in sharepoint, teams and outlook.
I have uploaded it in sharepoint, and then added it to teams so that it is available as an app in teams and outlook
The webpart works fine in teams, via browser in chrome and via the mac desktop application
However, it only works in the browser version of outlook, and only in chrome, not in safari, and therefore doesn't work in the iOS outlook app, because it uses safari (is my understanding).
I get the error "Refused to display 'https://login.microsoftonline.com/...' in a frame because it set 'X-Frame-Options' to DENY"
I have tested with the default helloworld webpart, that is created with yeoman, and I get the same issue

Steps to reproduce
  1. Create a new webpart using yeoman with React as the framework
  2. Deploy the app to your sharepoint tenant
  3. Add the app to Teams (also via sharepoint)
  4. Make sure the app is accessible to your user in the teams admin portal
  5. Open the webpart in outlook in safari (https://outlook.office.com)
Expected behavior

The webpart loads in safari without error as it does in other browsers

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.