This is a migrated thread and some comments may be shown as answers.

BUG: RadToolTip - HideEvent:LeaveTargetAndToolTip Not Working as expected

6 Answers 217 Views

ToolTip

This is a migrated thread and some comments may be shown as answers.

6 Answers, 1 is accepted

Accepted

answered on 22 Apr 2009, 03:17 PM

Hello Guido,

Thank you for reporting this, we are aware of it and what actually happens is this setting does not respect the AutoCloseDelay. However, we are still considering making the autoclose obsolete and that is why we haven't fixed this yet but it is in our TODO list.

For the time being in order to get the desired result I can suggest you to use one of the following approaches:

Override the default behavior and respect the autoclose by including the following script:

    
                        <script type="text/javascript">  
            
                    Telerik.Web.UI.RadToolTip.prototype._oldResetAutoCloseDelay = Telerik.Web.UI.RadToolTip.prototype._resetAutoCloseDelay;  
            
                    Telerik.Web.UI.RadToolTip.prototype._resetAutoCloseDelay = function()      
            
                    {  
            
                        this.cancelAutoCloseDelay();  
            
                        if (this.get_leaveTargetAndToolTip()) return;  
            
                        this.oldResetAutoCloseDelay();     
            
                    };  
            
                        </script>

Set a very big value for the AutoCloseDelay property.

Sincerely yours,
Svetlina
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

answered on 09 Jan 2015, 09:11 AM

video.zip

Hi David,

The AutoCloseDelay property of the tooltips defaults to 3000ms so tooltips close automatically after that delay if there is no user action (e.g, the mouse being moved even a bit so the mouseover events fire).

To disable this feature, set the AutoCloseDelay property to 0 as shown in the following articles:

I am also attaching here a short video that demonstrates the expected behavior as a reference so you can confirm if I am missing something.

As for the 6 year delay - as Svetlina noted, we were considering whether the HideEvent setting should override the AutoCloseDelay, but we decided it should not, as this would make the automatic closing useless. For example, in the OS, tooltips hide automatically after a few seconds as well. Thus, we decided to keep both properties and let the developers choose the behavior. The only HideEvent that overrides AutoCloseDelay is ManualClose, as it must require a user action.

Regards,

Marin Bratanov
Telerik

Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

answered on 01 Jun 2016, 10:09 PM

Hello Marin,

I think this information about setting AutoCloseDelay = 0 should be on the demo page that David mentions. That page is dedicated to demonstrating and explaining the ToolTip "Hide on Event".

Without this information, it makes nearly all the statements on the page incorrect and you will have a lot of developers thinking the control has a bug.

For instance: Default - hides when mouse is out of the target element

This is not true. It's really - hides when mouse is out of the target element or after mouse has been inactive in the target element for 3 seconds.

Many of us want to leave the tip open, particularly if the tip may take longer than 3 seconds to read. So when we read this page, we assume we can achieve what is stated and we will not be able to guess that we have to set the AutoCloseDelay to 0.

I suggest putting this information above the Radio Buttons that allow the user to test the different hide events.

Thanks,

Jon