fix(tooltip): preserve ButtonGroup context for tooltip-wrapped buttons

[wanxiankai]

Summary

• Add generic internal child-prop forwarding for transparent trigger wrappers.
• Preserve ButtonGroup direct-child semantics while allowing group props through Tooltip, Dropdown, Popover, Modal, Drawer, and AlertDialog.
• Keep wrappers independent of Button/ButtonGroup internals and prevent internal props from reaching DOM elements or separators.
• Add ButtonGroup stories covering Tooltip and Dropdown wrappers.
• Fixes [BUG] - ButtonGroup variant/size props don't propagate to Button when child is wrapped in Tooltip #6516

Verification

• pnpm typecheck:react
• pnpm lint:react
• pnpm build
• SSR regression checks for every supported wrapper, nested and fragment forwarding, and internal-prop leakage.

[vercel]

@wanxiankai is attempting to deploy a commit to the HeroUI Inc Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
heroui	Ready	Preview	Jul 30, 2026 4:17am
heroui-sb	Ready	Preview	Jul 30, 2026 4:17am

[wingkwong]

please verify locally once first before making a PR. The changes failed all QA.

[wanxiankai]

Thanks for checking. You're right — the first version leaked the internal ButtonGroup marker into the exported Tooltip type, which caused the QA TypeScript/build failures:

TS4023: Exported variable 'Tooltip' has or is using name 'BUTTON_GROUP_CHILD'...

I pushed 5fb754d to keep the marker prop internal to the Tooltip implementation while preserving the same behavior. The new QA run is currently marked action_required before jobs execute, so I can't see the updated TypeScript/build result yet from my fork. Could you approve/re-run the workflow when you have a chance?

[wingkwong]

You may verify by running pnpm typecheck and pnpm build first.

[wanxiankai]

Thanks — I reproduced the issue locally on 5fb754d. pnpm typecheck still failed with the same TS4023 because TooltipRoot's inferred function signature included the internal computed marker prop.

I pushed d24d501 to explicitly expose TooltipRoot as React.FC<TooltipRootProps> while keeping ButtonGroupChildProps only in the implementation signature. The generated declaration now contains declare const TooltipRoot: React.FC<TooltipRootProps>; and no BUTTON_GROUP_CHILD reference.

Local verification now passes:

• pnpm typecheck
• pnpm build
• pnpm lint:react
• pnpm exec prettier --check packages/react/src/components/tooltip/tooltip.tsx

The new QA workflow run 30183835766 completed with no jobs, so it still needs approval/re-run from a maintainer.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@heroui/react@6730

npm i https://pkg.pr.new/@heroui/styles@6730

commit: 2a8a7ec

[wingkwong]

The scope is too narrow as you only cover Tooltip. Also it is a generic wrapper and should not know anything about Button or ButtonGroup internals. If the intent is "transparent wrappers forward unknown props to their first child", it should be implemented generically without importing Button.

[wanxiankai]

Thanks for the feedback. Updated in 2a8a7ec.

• Removed Tooltip's Button/ButtonGroup imports and special-case traversal.
• Added a generic internal child-prop forwarding mechanism for transparent trigger roots.
• Applied it across Tooltip, Dropdown, Popover, Modal, Drawer, and AlertDialog, with Button consuming the forwarded props.
• ButtonGroup only marks opted-in direct children, preserving direct-child semantics and preventing internal props from reaching DOM elements or separators.
• Added ButtonGroup stories covering Tooltip and Dropdown wrappers.

Verified with pnpm typecheck:react, pnpm lint:react, pnpm build, and SSR checks covering every supported wrapper, nested wrappers, fragments, and internal-prop leakage.

Could you please take another look?