Bug - Popper - Menus are hidden when used within content views

[Venefilyn]

Describe the problem
Menus and other components that use poppers consistently position themselves outside the content area when used within components that limit the content view, such as iframes.

This causes issues where scrollbars are not shown and menu is cropped without being able to click all menu items. There is no way AFAICT that would allow us to override popper offsets or otherwise indicate the available content view the popper should be visible within.

How do you reproduce the problem?
TODO
Provide steps to reproduce. A codesandbox demonstrating the problem is appreciated.

Expected behavior

• Popper does not go outside content views, if it does it should be scrollable.
• Popper should be configurable to handle custom scenarios like our iframe usage.

Is this issue blocking you?
Yes, it is a release blocker for Fedora 43. No good workaround known. This occurs within Anaconda Installer where an iframe is being used to serve Cockpit storage page.

Screenshots

What is your environment?

• OS: Linux
• Browser: Any

What is your product and what release date are you targeting?

• Anaconda Installer, Fedora 43 Beta
• Cockpit v347, 2025-09-17 (dependency of Anaconda Installer)

Any other information?

• https://bugzilla.redhat.com/show_bug.cgi?id=2388785
• https://pagure.io/fedora-qa/blocker-review/issue/1873
• storage: anaconda: fix: partition menu hidden behind non-scrollable content cockpit-project/cockpit#22381
• Popovers can be partially hidden in PF6 cockpit-project/cockpit#21922
• Related to Bug - Dropdown/Popper - Positioning is out of bounds in RTL near frame edge #11778

CC @mcoker @nicolethoen @thatblindgeye @garrett @bruno-fs

[kmcfaul]

Popper should expose customization for its offset property to allow custom calculation.

This also happens on lower resolutions (sub 720p), where the flip doesn't happen when it should. We may want to revaluate the defaults of offset/flip behavior later on.

[Venefilyn]

Popper should expose customization for its offset property to allow custom calculation.

Related to this part of the code. PF's Popper wrapper only has distance prop exposed which can only allow offset to be a single number.

patternfly-react/packages/react-core/src/helpers/Popper/Popper.tsx

Lines 412 to 444 in 7a5d71d

	const {
	styles: popperStyles,
	attributes,
	update,
	forceUpdate
	} = usePopper(refOrTrigger, popperElement, {
	placement: getPlacementMemo,
	modifiers: [
	{
	name: 'offset',
	options: {
	offset: [0, distance]
	}
	},
	{
	name: 'preventOverflow',
	enabled: preventOverflow
	},
	{
	// adds attribute [data-popper-reference-hidden] to the popper element which can be used to hide it using CSS
	name: 'hide',
	enabled: true
	},
	{
	name: 'flip',
	enabled: getPlacementMemo.startsWith('auto') || enableFlip,
	options: {
	fallbackPlacements: flipBehavior === 'flip' ? [getOppositePlacementMemo] : flipBehavior
	}
	},
	widthMods
	]
	});

We should remove distance prop and change the offset completely to something like this for complete configuration of it

modifiers: [
      {
        name: 'offset',
        options: offset
      },

[bruno-fs]

We should remove distance prop and change the offset completely to something like this for complete configuration of it

I guess it could default to current behavior if the user doesn't provide offset.