fix(Tooltip): expose strategy prop

[huntabyte]

No description provided.

[changeset-bot]

🦋 Changeset detected

Latest commit: fede373

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
bits-ui	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Copilot]

Pull Request Overview

Expose the Tooltip Content positioning strategy prop so consumers can control Floating UI’s positioning behavior.

• Replace narrow Pick of FloatingLayerContentProps with a broad Omit to include strategy
• Wire the new strategy prop through tooltip-content.svelte to useFloatingContent

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
packages/bits-ui/src/lib/bits/tooltip/types.ts	Broadens TooltipContentProps to include most FloatingLayerContentProps (to expose strategy).
packages/bits-ui/src/lib/bits/tooltip/components/tooltip-content.svelte	Adds strategy prop and forwards it to useFloatingContent.
.changeset/yummy-dolls-tell.md	Documents the patch change to expose strategy.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Switching from a targeted Pick to a broad Omit exposes almost all FloatingLayerContentProps, not just strategy. This widens the public API surface for TooltipContent beyond the stated goal and risks conflicts with DismissibleLayerProps where keys overlap. Recommend reverting to Pick and explicitly adding 'strategy' to the allowlist to avoid unintended prop exposure.

Suggested change

	Omit<FloatingLayerContentProps, "content" | "preventScroll"> &
	Pick<FloatingLayerContentProps, "strategy"> &

[github-actions]

📦 Bundle Size Analysis

📊 Modified Components

Component	Current	New	Change
🔴 Tooltip	112.62 KB gzipped: (35.65 KB)	112.67 KB gzipped: (35.66 KB)	+0.04 KB gzipped: (+0.01 KB)

---

📋 Understanding Bundle Analysis

• Individual Import Cost: Each component is measured in isolation, including all its dependencies
• Real-world Usage: When multiple components are used together, shared dependencies are deduplicated thus the actual bundle size is smaller than the sum of the individual component sizes
• Thresholds: Changes smaller than 0.01 KB or 0.1% are considered insignificant
• Gzipped Size: Represents the compressed size served to users

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
bits-ui	✅ Ready (View Log)	Visit Preview	fede373