You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a registered button is clicked and the timer is started, the "running" class is applied by harvest's JS. However if you come back to that button (either after a page load, or dynamic UI change and the button is recreated, and registered) the button doesn't get the "running" class applied to it.
Is this a bug? It seems counter to the usefulness of the button!
Is there any way for us to manually determine the state of a timer and apply a running class ourselves?
The text was updated successfully, but these errors were encountered:
If a registered button is clicked and the timer is started, the "running" class is applied by harvest's JS. However if you come back to that button (either after a page load, or dynamic UI change and the button is recreated, and registered) the button doesn't get the "running" class applied to it.
Is this a bug? It seems counter to the usefulness of the button!
Is there any way for us to manually determine the state of a timer and apply a running class ourselves?
The text was updated successfully, but these errors were encountered: