Closed grctest closed 11 months ago
When the refresh timer passes, the queries are refetched, during this period there are skeleton rows shown.
10+ rows looks unsightly
When there were previously "no orders found", showing 10+ skeleton rows only to then show "no orders found" is jarring.
Perhaps we should just maintain the last shown data whilst the refresh is occurring, and not show a refresh animation?
If we do continue showing the skeleton rows, then we should base the row qty on the previous row qty, to reduce layout shift.
A fix is now in place for the limit orders
When the refresh timer passes, the queries are refetched, during this period there are skeleton rows shown.
10+ rows looks unsightly
When there were previously "no orders found", showing 10+ skeleton rows only to then show "no orders found" is jarring.
Perhaps we should just maintain the last shown data whilst the refresh is occurring, and not show a refresh animation?
If we do continue showing the skeleton rows, then we should base the row qty on the previous row qty, to reduce layout shift.