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
We already support a "no data" UX for our pages, which is the loading data with pulsing placeholders. As was suggested by @mtias, for an offline state for a component that is missing data, our MVP approach could be to just show the placeholders without the pulsing animation. This could initially be as simple as removing the pulse animation effect when offline.
The text was updated successfully, but these errors were encountered:
We have an offline indicator on the page now and some design guidelines. Past that, it will be a very custom decision how to present offline for each component. So I would call this addressed.
We should still try to disable the placeholders as a raw solution across the app. Otherwise it will feel awkward until people get to update all the components.
We already support a "no data" UX for our pages, which is the loading data with pulsing placeholders. As was suggested by @mtias, for an offline state for a component that is missing data, our MVP approach could be to just show the placeholders without the pulsing animation. This could initially be as simple as removing the pulse animation effect when offline.
The text was updated successfully, but these errors were encountered: