Issue Summary

There is an inconsistency in the styling behavior between the confluence:globalPage and confluence:globalSettings modules in Confluence. Specifically, the way the iframe height is determined differs between the two.

Steps to Reproduce

1. Create a Custom UI app with both globalPage and globalSettings modules
2. Observe the difference of how the iframe height is rendered
3. In globalPage, if your parent div height isn’t explicitly defined, and the child page inherits the height of the parent div, the app is hidden since the height of the iframe itself is auto.

Expected Results

The confluence:globalPage module should behave consistently with the confluence:globalSettings module. Implementing a minimum height when child components' heights depend on their parent container can ensure that the iframe provides adequate space for initial layout calculations.

Actual Results

• confluence:globalPage Module: The iframe's height dynamically adjusts based on the height of its internal content, matching the height of its tallest child component.

• confluence:globalSettings Module: The iframe height appears to follow a different resolution strategy, possibly maintaining a minimum height to prevent it from collapsing.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available