fix(content): automatically recalculate offset when header/footer changes #30862
+197
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nges Previously, ion-content only calculated layout offsets on initialization or window resize. This caused content to be covered or obscured if a header or footer's dimensions changed dynamically (e.g. expanding a searchbar) or if they were added conditionally to the DOM. This implementation adds a ResizeObserver to watch sibling headers/footers for size changes and a MutationObserver to detect when they are added, triggering an automatic recalculation of the --offset-top and --offset-bottom CSS variables. Fixes ionic-team#26981
|
@HappyKnuckles is attempting to deploy a commit to the Ionic Team on Vercel. A member of the Team first needs to authorize it. |
ShaneK
requested changes
Dec 23, 2025
Member
ShaneK
left a comment
ShaneK
left a comment
There was a problem hiding this comment.
Thanks for your PR! This is looking really good! Aside from the broken tests, this is what I would like to see changed
|
|
||
| for (const mutation of mutations) { | ||
| if (mutation.type === 'childList') { | ||
| mutation.addedNodes.forEach((node: any) => { |
Member
There was a problem hiding this comment.
I think you can just use HTMLElement for this? Shouldn't need to use any, preferably
Author
There was a problem hiding this comment.
I typed it as Node and checked for instanceOf HtmlElement in the loop.
| } | ||
| }); | ||
|
|
||
| mutation.removedNodes.forEach((node: any) => { |
Member
There was a problem hiding this comment.
I think you can just use HTMLElement for this? Shouldn't need to use any, preferably
…afety for MutationObserver
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue number: resolves #26981
What is the current behavior?
Currently, ion-content calculates its layout offsets (--offset-top/bottom) only on initialization or window resize.
If a developer dynamically changes the height of a header or footer (e.g., expanding a searchbar, wrapping text) or adds a toolbar conditionally to the DOM (e.g., via *ngIf), the ion-content does not adjust. This results in content being obscured behind the header/footer.
What is the new behavior?
This PR adds a ResizeObserver and MutationObserver to ion-content to automatically handle dynamic layout changes.
ResizeObserver watches sibling and elements and triggers a recalculation of --offset-top and --offset-bottom whenever their dimensions change.
MutationObserver watches the parent element to detect when or elements are added to or removed from the DOM.
Removes the need for developers to manually listen for standard dynamic layout changes.
Does this introduce a breaking change?
Other information
I have added a new E2E test suite in core/src/components/content/test/auto-offset which covers:
Visual Regression: Ensures no regressions on initial load.
Functional Header: Expands a header dynamically and asserts that content --offset-top update correctly.
Functional Footer: Expands a footer dynamically and asserts that content --offset-bottom update correctly.
Visual Confirmation: Snapshots verify that the content is physically pushed down/up when toolbars expand.
Before:
After:
