Problem:
We want the simple table to have a loading state
Screenshots/mockups:
TODO
Acceptance criteria:
- basic table component has a loading state
Lydia_Pintscher | |
Aug 27 2021, 9:30 AM |
F34626529: Screenshot 2021-08-31 at 11.24.02.png | |
Aug 31 2021, 9:24 AM |
Problem:
We want the simple table to have a loading state
Screenshots/mockups:
TODO
Acceptance criteria:
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Sarai-WMDE | T289053 [Epic] Create Simple Table component | |||
Resolved | ItamarWMDE | T290953 Results page - confirmation of review decision submission | |||
Declined | None | T289844 loading state of simple table component |
In the context of the Mismatch Finder single page application, the results page will only be loaded once the relevant mismatches are available to be displayed. The progress on the server side is communicated to users via the indeterminate loader in the TextArea component of the form page. Therefore, tables do not need a loading state because they won't be displayed until results are processed. This ticket needs to be declined.
Nevermind! Itamar gave me a heads-up that we may want to display a loader whenever users apply the changes they made to the Status using the dropdowns included in the table.This should be confirmed with @Mattia_Capozzi_WMDE's help, and designs might need a seconf thought, as displaying a skeleton might not be the best in this situation (maybe we can apply a subtle overlay in the context of the app, so the content of the table remains visible?)
During our Design review session today, we decided that under no circumstances would we need to incorporate a loadingstate to the table component at this time: in the context of the Mismatch finder, the indication that changes are being applied to the table will be handled by the application.