Currently updates to the in-browser database (IndexDB) result in re-rendering the corresponding HTML table (view) even if the table is on a hidden tab. Further, updates awkwardly may interrupt users clicking on rows in the table to select them. We need to only re-render the currently visible table and perhaps only when initially navigated to. Instead of async re-draws, perhaps show a stale data indicator when updates occur and allow users to refresh on their own time? Or perhaps show an auto-refresh timer count-down so users know when the whole table of is about to change under them (resetting the selection and otherwise making it difficult to interact). This is especially problematic with activations as they are currently updating the table once a second, making it difficult to interact with. To be fair, these are nuisance alarms and the goal with the alarm system is notifications at a frequency that an operator can reasonably perform a corrective action on (which is likely a handful an hour, not one a second). Needs some thought.
slominskir
commented
2 years ago
Currently updates to the in-browser database (IndexDB) result in re-rendering the corresponding HTML table (view) even if the table is on a hidden tab. Further, updates awkwardly may interrupt users clicking on rows in the table to select them. We need to only re-render the currently visible table and perhaps only when initially navigated to. Instead of async re-draws, perhaps show a stale data indicator when updates occur and allow users to refresh on their own time? Or perhaps show an auto-refresh timer count-down so users know when the whole table of is about to change under them (resetting the selection and otherwise making it difficult to interact). This is especially problematic with activations as they are currently updating the table once a second, making it difficult to interact with. To be fair, these are nuisance alarms and the goal with the alarm system is notifications at a frequency that an operator can reasonably perform a corrective action on (which is likely a handful an hour, not one a second). Needs some thought.