Issue with hovering on custom tooltips

[v3gard]

Describe the bug If custom tooltips are required, hovering doesn't work as expected as the "ease-out" fade transition on the hiding element fails to run.

A workaround is to add the following class style:

[class*="ag-tooltip-hiding"] {
        display: none;
    }

To Reproduce Steps to reproduce the behavior:

1. Create an AG grid table
2. Add a custom tooltip
3. Add fusion styling
4. See example here.

Expected behavior Ease-in and Ease-out transition works "out of the box", just in the official demos.

Screenshots	Issue	Workaround

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Chrome
• Version: 118.0.5993.89

[odinr]

created a PR, will this fix your issue. Will this affect anyone not using custom tooltips (except fading out)?

can create a snapshot for testing if needed?

not to familiar with AG-Grid but can have @eikeland have a look

[v3gard]

Will this affect anyone not using custom tooltips (except fading out)?

Vet ikke. Jeg forstår ikke helt hvorfor vi må ha denne hack'en i utgangspunktet. Default AG grid oppfører seg ikke slik med custom tooltips.

can create a snapshot for testing if needed?

@odinr: Ja, takk. Tar gjerne en pakkereferanse som vi kan teste via npmjs

[eikeland]

@v3gard Do the issue persist when setting attribute tooltipHideDelay={0}?

[odinr]

created a snapshot @equinor/fusion-react-ag-grid-styles@issue-1148

[v3gard]

@eikeland @odinr It seems the issue is solved in the newest version of the involved packages, and that we can remove our local hack. I tested this using the CPR app with this package.json. I.e. the fade-out effect has started working (as it does in vanilla AG Grid without Fusion styling)

• AG-Grid: 30.2.1
• fusion-framework-module-ag-grid: 30.2.0
• fusion-react-ag-grid-styles: 30.2.0

This means that there's no need for the snapshot you created @odinr.

Can you also confirm this @AndreasPresthammer?

1. We can remove our local hack.
2. Custom tool tips still works (without the wonky UI error as initially described in this issue)

In that case, we can close this ticket.

[AndreasPresthammer]

@v3gard yes, it seem to work fine now 👌

[odinr]

@v3gard @AndreasPresthammer, so it works now without the css hack in https://github.com/equinor/fusion-react-components/pull/1325?

[v3gard]

@odinr Yes.