Repository navigation
SPFx 1.21 RC flexibleLayoutSizing value of supportsDynamicResizing in web part's manifest #10197
Description
What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
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
- browser version: 135.0.7049.85
- SPFx version: 1.21.0-rc.0
- Node.js version: v22.14.0
Issue description
In the latest SPFx version 1.21 RC the support to flexible layout was introduced.
I've checked the release notes where the following code sample is shown:
"flexibleLayoutSizing": {
"supportsDynamicResizing": true,
"defaultRowHeight": 10,
"defaultColumnWidth": 10
}However I don't understand how the supportsDynamicResizing should work.
I've tried changing it, repackaging the solution and redeploy it but it doesn't seem to have any effect.
Can someone help me understand how this should work? Is the support to this configuration still in the rolling out phase?
Thanks in advance!
Activity
Amey-MSFT commentedon Apr 17, 2025
Hello Guido Zambarda (@GuidoZam) ,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
Haiqi-Wu commentedon Apr 17, 2025
By default all custom web parts are supported in the flexible layout option and don't require any code level changes.
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/release-1.21#flexible-layout-configuration-options-for-web-parts
https://techcommunity.microsoft.com/blog/spblog/introducing-flexible-sections-in-sharepoint-pages-and-news/4170031
GuidoZam commentedon Apr 17, 2025
Thanks Amos_Wu (@Haiqi-Wu) for the reply, I already know that, my point was to understand what that configuration value does.
StfBauer commentedon Apr 17, 2025
Better don't use it any can take full advantage of the flexible Layout zone. ;)
GuidoZam commentedon Apr 17, 2025
Sure thing Stefan Bauer (@StfBauer) I agree with you, I just wanted to understand what it does. Since I've tried setting the value of
supportsDynamicResizingto false, and yet the web part act as if it is set to true, I don't get if either it's not working on my tenants yet or if there's a bug on the handling of this setting.Amey-MSFT commentedon Apr 17, 2025
Hello Guido Zambarda (@GuidoZam) ,
In the latest SPFx version 1.21 RC, the
supportsDynamicResizingproperty in theflexibleLayoutSizingconfiguration is intended to enable dynamic resizing of web parts within flexible layouts. When set to true, it should allow web parts to adjust their size automatically based on the layout context and specified default dimensions (defaultRowHeightanddefaultColumnWidth).So, regarding if the configuration is still in the rolling out phase, might be why the solution does not have any effect,
Will connect with the engineering team and let you know the updates.
Thanks!!
GuidoZam commentedon Apr 17, 2025
Thanks for the update Amey-MSFT!
VesaJuvonen commentedon Nov 3, 2026
This issue is more than 12 months old and has not had recent activity. We are cleaning up the backlog so we can manage incoming reports more efficiently. If the issue is still relevant, please submit a new issue with updated details and current reproduction steps. We apologize for any inconvenience caused by this updated process, and thank you for being part of the SharePoint developer ecosystem.
github-actions commentedon Nov 3, 2026
Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.
If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.
We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.