Often, the user will take an action that requires a network fetch before we know what to render, e.g. when you select a ZObject on Special:EvaluateFunctionCall. In the second or two before we have content to show, we should show a spinner, pending placehoder, or some other widget that demonstrates that things are happening in the background, rather than leaving the user to just hope.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T313819 Papercut: When fetching the data about a ZObject, show a pending animation state rather than just no response | |||
| Open | None | T311874 [New component] Skeleton: Add Skeleton loader component to Codex | |||
| Open | None | T397109 Image: Add loading (Skeleton) state | |||
| Resolved | SGautam_WMF | T345921 [EPIC] ProgressIndicator: Add ProgressIndicator component to Codex | |||
| Resolved | SGautam_WMF | T367097 ProgressIndicator: Figma spec and Guidelines | |||
| Resolved | Volker_E | T373218 ProgressIndicator: Introduce a WIP component | |||
| Duplicate | Volker_E | T373219 ProgressIndicator: Add CSS-only version | |||
| Duplicate | Volker_E | T373220 ProgressIndicator: Add component guidelines | |||
| Resolved | Volker_E | T373222 ProgressIndicator: Take out of WIP | |||
| Resolved | SGautam_WMF | T377493 ProgressIndicator: redesign from bouncing dots to spinner |
Event Timeline
Comment Actions
I'm assuming a codex component is preferable? I only currently see a progress bar available for loading. @AAlhazwani-WMF any thoughts?