Remove will-change: width and use actual element height in PageLayout drag optimizations #7374
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removes ineffective
will-change: widthoptimization and fixes layout shift from hardcoded size estimation in PageLayout drag operations.Changes
paneUtils.ts:will-change: widthfrom drag styles—provides no benefit for layout properties, only increases memorycontainIntrinsicSizefrom hardcoded500pxto actualelement.offsetHeightto prevent layout shift withcontent-visibility: autoPageLayout.test.tsx:will-changeis no longer applied during drag operationsChangelog
Changed
PageLayout.Pane: Removedwill-change: widthduring resize/drag operationsPageLayout.Pane:containIntrinsicSizenow uses actual element height instead of hardcoded 500pxRollout strategy
Testing & Reviewing
Test resizable panes in PageLayout stories—drag behavior should be unchanged, but more efficient.
Merge checklist
Original prompt
This pull request was created from Copilot chat.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.