Skip to content

ToolbarItem - props for width and flex-grow #11910

Description

@mcoker

Looks like we used to have a widths prop for <ToolbarItem /> that was commented out in a core bump (and later removed) - #10022. Digging into that, it looks like it was because the CSS variables used with that prop were removed accidentally (https://github.com/patternfly/patternfly/pull/6057/files), which probably broke the core bump, so that feature was commented out. Then we added the vars back in core (https://github.com/patternfly/patternfly/pull/6302/files) and never added the widths prop back.

Also there is a .pf-m-flex-grow[on-{breakpoint}] modifier in core that can go on <ToolbarItem /> and <ToolbarGroup /> that we should add a react prop for.


Jira Issue: PF-2344

Activity

  1. added theissue type on Jul 2, 2025
  2. moved this from Needs triage to Ready to assign in PatternFly Issueson Jul 21, 2025
  3. github-actions commented on Sep 5, 2025

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

  4. khadesamrudhi commented on Oct 20, 2025

    @khadesamrudhi

    Hi!
    I’d like to work on this issue. I’ve implemented a fix locally to add widths and flex-grow responsive props for ToolbarItem, ensuring proper handling for both default and breakpoint-specific classes.
    I’ll open a PR shortly to address this issue.

  5. khadesamrudhi commented on Oct 20, 2025

    @khadesamrudhi

    Opened PR #12074 to address issue #11910.

  6. github-actions commented on Dec 20, 2025

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

  7. 1 remaining item

  8. moved this from Ready to assign to PR Review in PatternFly Issueson Jan 12, 2026
  9. added a commit that references this issue on Feb 6, 2026
    f9fe659
  10. github-actions commented on Feb 24, 2026

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

  11. github-actions commented on Apr 26, 2026

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

  12. github-actions commented on Jun 30, 2026

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

  13. added a commit that references this issue on Aug 3, 2026
    4916846
  14. added a commit that references this issue on Aug 3, 2026
    8e610ef
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions