patternfly / patternfly/patternfly-react

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

Open
#12,611 6 comments 1 reaction 1 assignee View on GitHub

@jcmill is already working on this.

Since Jul 22, 2026.

Dominant language
TypeScript
Stars
862
Forks
392
Avg merge
4d 8h
Merged PRs (30d)
9

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.