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
Describe the bug
I have a pop-up for a flip down timer card. IF "background_upate: false", the card only shows the original timer duration. If I set "background_update: true", then the card will countdown until I close the card. If I close the card or navigate to another page and then open the timer card popup again, the timer card shows whatever the remaining time is at that moment, but it does not update any further.
To Reproduce
Steps to reproduce the behavior:
Create popup card using flipdown timer card
Activate popup
Observer card not updating as it should
Expected behavior
Timer card should update and show "counting down" whenever it is open and there is an active timer
I've done further testing, and I believe it definitely has something to do with the bubble pop-up card implementation. If I take the same timer card, and place it in its own dashboard view, and then navigate to that page when necessary, I cannot observe this issue. The timer card works as expected everytime, whether navigating to the page by click, or programmatically via automation and browser_mod call. I wanted to rule out the timer card itself and I believe I've done that.
Describe the bug
I have a pop-up for a flip down timer card. IF "background_upate: false", the card only shows the original timer duration. If I set "background_update: true", then the card will countdown until I close the card. If I close the card or navigate to another page and then open the timer card popup again, the timer card shows whatever the remaining time is at that moment, but it does not update any further.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Timer card should update and show "counting down" whenever it is open and there is an active timer
YAML
Informations (please complete the following information):
Additional context
possibly related to #1324
The text was updated successfully, but these errors were encountered: