Tooltip.Provider can't set defaults for most Tooltip.Root settings

[pepkin88]

Describe the bug

The documentation says, that "...[Tooltip.Provider] provides shared state for the tooltip components used within it". And then there is example with delayDuration and disableHoverableContent.

But is seems that those are the only props, that we can set defaults for, because all the other ones are auto-initialized in Root, and only nullish values can fall back to those set in the Provider.
So for example, if I want to have the value of disableCloseOnTriggerClick be read from the Provider, I can't do that, because if I then put <Tooltip.Root> without disableCloseOnTriggerClick prop, it would initialize to false and won't use the Provider's value.
I could work around it by setting those values on Root, but that'd defeat the purpose of having common settings in the Provider. I could also set those values to null, but that is not an accepted type for those fields.

This is the fragment in "tooltip/components/tooltip.svelte" that auto-initializes those values:

	let {
		open = $bindable(false),
		onOpenChange = noop,
		disabled = false,
		delayDuration,
		disableCloseOnTriggerClick = false,
		disableHoverableContent,
		ignoreNonKeyboardFocus = false,
		controlledOpen = false,
		children,
	}: TooltipRootProps = $props();

I think it's a mistake, because in "tooltip-provider.svelte" those props are exposed to be set as defaults.

Reproduction

https://stackblitz.com/edit/vitejs-vite-esq3cy?file=src%2FApp.svelte

Logs

No response

System Info

System:
    OS: macOS 14.5
    CPU: (10) arm64 Apple M1 Pro
    Memory: 126.45 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.17.0 - /usr/local/bin/node
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.9.0 - /usr/local/bin/pnpm
    bun: 1.0.14 - ~/.bun/bin/bun
  Browsers:
    Chrome: 130.0.6723.92
    Chrome Canary: 132.0.6817.0
    Safari: 17.5
    Safari Technology Preview: 18.0
  npmPackages:
    @sveltejs/kit: ^2.7.2 => 2.7.2
    bits-ui: 1.0.0-next.38 => 1.0.0-next.38
    svelte: ^5.1.0 => 5.1.0

Severity

annoyance

[pepkin88]

BTW, I had to set interactOutsideBehavior="ignore" in Content, in order to be able to see the effect of disableCloseOnTriggerClick, because any pointerdown event on the trigger element would close the tooltip immediately.
Maybe the trigger element shouldn't be treated as something "outside"?

[huntabyte]

Looking into this!

[huntabyte]

Closed as fixed in bits-ui@1.0.0-next.44