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 user selects/deselects event(s) via checkbox while table poll is ongoing, the checkbox erroneously changes state but the selection changes are not persisted. After table poll is completed the UI changes to the affected checkbox(es) disappear as well indicating to the user that changes attempted during table poll were not persisted.
If it is not possible to perform concurrent operations during table poll, all other operations should be disabled during table poll (page overlay with loading indicator for example).
Alternatively a different and a more efficient event update mechanism than poll of the entire table (#4) could potentially automatically solve this bug.
The text was updated successfully, but these errors were encountered:
Table refresh with ntie #87 introduces a much more efficient rows update mechanism and thereby dramatically reduces the 'surface area' for this bug to occur.
Also HTMX requests synchronization in Table refresh with ntie #87 fixes the row-selection-state aspect of this bug. Meaning that if user via checkbox selects several rows while some other request is ongoing, all those changes will eventually be persisted in the app session and therefore in the view.
Not yet fixed:
Misleading UI of the checkbox in the indeterminate state, ie state where user has ticked the checkbox but the request was not yet processed. The row seems erroneously selected due to CSS browser defaults for the checkbox input tag, see the Indeterminate checkbox in the example below:
The browser defaults for [type="checkbox"]:checked need to be removed.
If user selects/deselects event(s) via checkbox while table poll is ongoing, the checkbox erroneously changes state but the selection changes are not persisted. After table poll is completed the UI changes to the affected checkbox(es) disappear as well indicating to the user that changes attempted during table poll were not persisted.
If it is not possible to perform concurrent operations during table poll, all other operations should be disabled during table poll (page overlay with loading indicator for example).
Alternatively a different and a more efficient event update mechanism than poll of the entire table (#4) could potentially automatically solve this bug.
The text was updated successfully, but these errors were encountered: