As a wikidata user
I want my edits made on mobile to be saved
So that I can actually contribute
A/C
- User can enter in the simple text input (string)
- qualifiers, references, and ranking remain read-only (functionality will be handled in T402618)
- the publish button saves edits
- the publish button only functions if the edits made are valid
- When the user clicks publish the button becomes disabled, so the user doesn't bomb click it.
- invalid edits (validation errors) are marked in the appropriate location in codex red
- ( (!) I think this will be covered already in M3.1.1)
- while we wait for the server to process the save, we remain on the dialog page
- The user stays in the editing page until the server responds positively or negatively.
- (!) A loading spinner will be used - https://doc.wikimedia.org/codex/main/components/demos/progress-bar.html (UX remains TBD)
- It should appear with a transition: Fade in (component option)
- if successful
- the user is redirected to the same location they were at previously (use the same functionality as in T401403)
- the confirmation popup is displayed at the bottom of the page
- the success popup is the codex component (and has a predefined time of how long it lasts on screen)
- if the save is unsuccessful
- the user remains on the edit statement dialog page
- the appropriate error handling is used (for this ticket a placeholder is good enough, detailed error handling will be in T403011)
- the user is informed of the unsuccessful save and given an informative reason as to why the save was unsuccessful
- test are updated/created as needed
Open questions
- Where/when/ for how long does the successful pop up appear?
ANSWER:
The codex component Message will appear when the publishing is successful or unsuccessful (component provides both actions). User stays in the page until the server returns an answer:
If successful: the user returns to the previous screen where he can admire his work and the success message shows up there.
If it fails: the user stays in the editing page, fail message appears on this page and explains reason of failure.
It should appear with a transition: Fade in (component option)
- Where/when/ for how long does the unsuccessful pop up appear?
ANSWER:
Where - The position is not specified on the description on codex (or i couldn't find it). Therefore, if there is no predefined position, place it at the bottom of the page as in the prototype from Larissa that was user tested.
For how long: The component has an option called auto-dismiss that allows the component to disappear. The transition is pre-defined.
- What happens between clicking “publish” and the server responding that the edit has been successfully saved? - - Do we show some kind of loading spinner? Do we close the edit form and wait until the server responds before showing the “succcess!” banner at the bottom? How do we display any errors the server might return (user blocked, AbuseFilter, etc.)?
ANSWER:
When the user clicks publish the button becomes disabled, so the user doesn't bomb click it.
The user stays in the editing page until the server responds positively or negatively.
A loading spinner will be added after first pass - UI refinement.
@karapayneWMDE & @Arian_Bozorg I suggest we create a ticket for all error behavior (extensive topic that should be handled consistently and holistically, and includes UX copy work.
T403011: [MEX] M3.1.2 - error handling while publishing/saving statement edits
Note: Adding qualifiers, references, and ranking will be handing in T402618: [MEX] M3.3 edit functionality for qualifiers, references, and ranking
0
Success popup
