patternfly / patternfly/patternfly-react

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

Abierto
#12,611 6 comentarios 1 reacción 1 asignado Ver en GitHub

@jcmill ya está trabajando en esto.

Desde el 22/7/2026.

Lenguaje dominante
TypeScript
Estrellas
862
Forks
392
Merge medio
4 d 8 h
PR fusionados (30 d)
9

Descripción

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

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.