Start a new pull request in StackBlitz Codeflow.

• kulxrc (Open reproduction)

You are welcome to open a PR for it 👍

I just need to remove the if condition completely.It's seems enough to make it working but I see many comits related to the IF condition in the past so I guess it's an intention to have it there, isn't it?
It has been reworked many times but my use case is to rollback it before the first change and just allow null, undefined or empty string. It does not cause any issues at the first glance in my test code.

What's the purpose of that IF condition?

Obviously removing the condition isn't the solution 🙂
If you have a nullish value, why do we need to create the tippy instance? we have nothing to show. we only need to create it in case we have a value to show in the tooltip.
The solution here is to create/destroy the instance depending on the content changes as well and not just on initialization.

I've come across this problem too.

It happens when the initial value is null or undefined, and it only gets provided after some time — a scenario that's quite common when working with ngrx, given that state can evolve from being nullish to having a concrete value. In these cases, the tooltip doesn't appear unless the [tp]="variable$ | push" or [tp]="variable()" is already set with a value that's not null or undefined initially.

I'm also seeing this problem when using pipe async.
For example:
[tp]="getMyTooltiptext() | async"
does not render a tooltip.