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?
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?