patternfly / patternfly/patternfly-react

Bug - FormFieldGroupExpandable - Horizontal line overlap, when no header is defined.

Offen
#12,611 6 Kommentare 1 Reaktion 1 zugewiesene Person Auf GitHub ansehen

@jcmill arbeitet bereits daran.

Seit 22.7.2026.

Vorherrschende Sprache
TypeScript
Sterne
862
Forks
392
Ø Merge
4 T. 8 Std.
Gemergte PRs (30 T.)
9

Beschreibung

Describe the problem
This is an issue with

  • Patternfly 5

  • Patternfly 6

  • other

This is a CSS layout bug in PatternFly's FormFieldGroupExpandable component. When the optional header is not provided, the expand/collapse toggle icon overlaps with the component's top border.

The issue stems from how the component handles the absence of a header. The CSS styling appears to rely on the header's presence to create the necessary vertical space for the toggle icon (the caret >). When the header is omitted, this space collapses, causing the icon to be misaligned and render directly on top of the horizontal line.

How do you reproduce the problem?
https://codesandbox.io/p/devbox/boring-germain-98h679?workspaceId=ws_M4PEkPeCW7FD8LFeSHjZJQ

Expected behavior
The expand/collapse toggle icon should be vertically aligned and have sufficient padding to ensure it does not overlap with the component's top border. This alignment should be maintained even when the optional header prop is not provided, ensuring the component renders gracefully in all its valid configurations.

Is this issue blocking you?
No, this is a visual bug and does not block functionality.

Screenshots

(no header)

image

(just action button)

image

What is your environment?
This issue is likely independent of the environment and appears to be a component styling bug.

OS: macOS

Browser: Chrome

Version: Latest versions

What is your product and what release date are you targeting?
N/A
Any other information?
N/A


Jira Issue: PF-4528

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.