SharePoint / SharePoint/sp-dev-docs

[SharePoint Copilot Apps preview] " IFrame/container height remains same in expand and collapse mode

Open
#10,989 5 comments 0 reactions 2 assignees View on GitHub

@jansenbe is already working on this.

Since Aug 26, 2026.

area:spfx area:spfx-copilot-apps Needs: Author Feedback sharepoint-developer-support 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

Windows

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

SPFx version. 1.24.0-beta.2
Node.js version : v22.21.1

Describe the bug / error

When an SPFx Copilot Component is rendered inside Microsoft 365 Copilot, the component iframe appears to use the same height in both collapsed and expanded states.

Expanding the component does not trigger a resize of the iframe/container height. As a result, the expanded view is constrained to the same height as the collapsed view.

From browser inspection, the iframe is rendered with a fixed height value:

Image
Steps to reproduce
  1. Create and deploy an SPFx Copilot Component.
  2. Open Microsoft 365 Copilot.
  3. Trigger a response that renders the component.
  4. Observe the component in collapsed state.
  5. Expand the component.
  6. Inspect the generated iframe/container element.
Expected behavior

The iframe/container height should be recalculated when the component is expanded so that the expanded content can be fully displayed.

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.