Completed
Last Updated: 05 Aug 2024 13:30 by ADMIN
Release 6.1.0
Sara
Created on: 01 Jul 2024 10:32
Category: Tooltip
Type: Bug Report
7
[Regression] Tooltip position doesn't change when the user move the cursor between two elements with small proximity
Hi,

The issue is that the tooltip position doesn't change when the user move the cursor between two elements with small proximity. 

The best example is Telerik's own Tooltip demo Blazor Components Demos and Examples - Telerik UI for Blazor. More often than not when moving between Karachi and Mumbay/Bombay tha tooltip doesn't shift position even though the text changes.
4 comments
ADMIN
Hristian Stefanov
Posted on: 25 Jul 2024 07:33

Hello,

I can confirm that this issue occurs with version 6.0.0, indicating it's a regression. As regressions are our highest priority, I have significantly increased the priority of this item in our backlog.

Regards,
Hristian Stefanov
Progress Telerik

Do you have a stake in the designеr-developer collaboration process? If so, take our survey to share your perspective and become part of this global research. You’ll be among the first to know once the results are out.
-> Start The State of Designer-Developer Collaboration Survey 2024

Matt
Posted on: 18 Jul 2024 19:48

I have experienced this too. I can also confirm that version 6.0 of Telerik UI for Blazor has brought this issue. Version 5.1.1 does not have this problem. I'm wondering if it has something to do with update below in 6.0. I have also put in some screenshots of what the problem looks like for us.

 

 

Christian
Posted on: 05 Jul 2024 06:18
The problem seems to occur, whenever the tooltip is not closing until a new tooltip content is provided (f.e. if you have buttons that directly next to each other). than the position remains on the first button that opens the popup, but the content will display the information of the hovered button ...
Christian
Posted on: 04 Jul 2024 11:46
I also experienced this today after upgrading to the latest version. we not changed any other code in this area. it seems that latest ui components release brought up this issue!