UI5 / UI5/webcomponents

ui5-form: FormGroup heading text overflows and overlaps content when group name exceeds fixed height

Open
#13,852 2 comments 0 reactions 1 assignee View on GitHub

@nnaydenow is already working on this.

Since Jul 27, 2026.

Medium Prio TOPIC Core
Dominant language
TypeScript
Stars
1.8k
Forks
285
Avg merge
3d 2h
Merged PRs (30d)
59

Description

Describe the bug

The .ui5-form-group-heading element inside ui5-form's shadow DOM is rendered with a fixed height (and matching line-height) driven by the CSS variable --_ui5-form-group-heading-height (default: 2.75rem, compact: 2rem):

  .ui5-form-group-heading {
    height: var(--_ui5-form-group-heading-height);
    line-height: var(--_ui5-form-group-heading-height);
  }

When a FormGroup's headerText is long enough to wrap onto multiple lines, the container does not expand — the text overflows the fixed-height box and visually overlaps the form items below it.

Isolated Example

https://stackblitz.com/edit/github-nc5aumrw-w6zbywej?file=src%2FApp.tsx

Reproduction steps
  1. Open the isolated example: https://stackblitz.com/edit/github-nc5aumrw-w6zbywej?file=src%2FApp.tsx
  2. Observe the FormGroup with the heading "Personal DataPersonal DataPersonal DataPersonal DataPersonal DataPersonal DataPersonal Data"
  3. Notice the group heading text overflows its fixed-height container and overlaps the form fields below it
Expected Behaviour

The heading container expands vertically to fit wrapped text. height should behave as min-height so short labels retain the standard row height while long labels grow to accommodate the content.

Screenshots or Videos
Image
UI5 Web Components for React Version

2.24.0

UI5 Web Components Version

2.24.0

Browser

Chrome, Edge, Firefox, Safari

Operating System

No response

Additional Context

No response

Relevant log output

Organization

No response

Declaration
  • I’m not disclosing any internal or sensitive information.

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.