# \[IGN-7682\] Disabled MultiState Button tooltip persists after mouse has left component

**URL:** <https://forum.inductiveautomation.com/t/ign-7682-disabled-multistate-button-tooltip-persists-after-mouse-has-left-component/73472>\
**Category:** Ignition\
**Tags:** perspective, ignition81\
**Created:** [May 9, 2023, 1:37pm UTC](https://forum.inductiveautomation.com/t/ign-7682-disabled-multistate-button-tooltip-persists-after-mouse-has-left-component/73472 "2023-05-09T13:37:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\
**Post date:** [May 9, 2023, 1:37pm UTC](https://forum.inductiveautomation.com/t/ign-7682-disabled-multistate-button-tooltip-persists-after-mouse-has-left-component/73472/1 "2023-05-09T13:37:49Z")

</div>

I have found that the tooltip on a multistate button, when the component is disabled (i.e. `enabled` = false), is persistent even after the mouse is moved from the component area. When enabled, it is persistent only when the mouse remains in the component area.

![Tooltips_Disabled](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/8/c81c33eb216ce9e3c9e67da1c78f48532284ecbd.gif)  
 ![Tooltips_Enabled](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/a/7a8f10d357423bb35cf8a38b50ae5bd70868850c.gif)

Not sure if this is the only component affected, but this is the only one I've noticed.

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [May 9, 2023, 5:17pm UTC](https://forum.inductiveautomation.com/t/ign-7682-disabled-multistate-button-tooltip-persists-after-mouse-has-left-component/73472/2 "2023-05-09T17:17:46Z")

</div>

I've opened an internal ticket to fix this behavior, as well as an associated issue I found while attempting to replicate the posted issue.
