Hello, when I type text every second or so something moves in my sight. A text message informs me that the text (I just typed in) has been saved. This text is more or less constantly moving and extremely annoying; when I am typing I am concentrating on my text and don't want to be distracted all the time. Can I turn it off?
Topic on Talk:Content translation
Well, technically there is a way—you can add the following to your global.css:
.cx-header__draft-status {
display: none;
}
Although I agree it's not the most convenient thing.
Our designer @Pginer-WMF should probably know about this.
Thank you - but it seems that I have no rights to create that page you linked to?
Hmm. I may have posted a wrong link.
Let's try something else: Can you please try going to your preferences, then to appearance and click "Custom CSS" under "Shared CSS/JavaScript for all wikis" (this is the second "Custom CSS" on that page; don't confuse it with "all skins"). That's supposed to be the page to edit. Does this work?
It works! Thanks a lot!
We should pay attention to this in upcoming research, since at this point we got reports that indicate both:
- Saving indicator being too prominent causing distraction.
- Saving indicator being ignored, causing the user to think their work was lost.
One solution we explored to avoid the 2nd problem was to make the auto-save more prominent the first time. Maybe if we also make it less prominent the following times it saves we can find the right balance. In this way it will be clear that the article is being saved automatically the first time for a translation but not causing distraction during the rest of the translation. In any case we need to explore and evaluate options to find the right balance.
Hello, thanks for the explanation. Maybe the user is happy with a button to save or to indicate the last date of autosave? That would give the user a feeling of being in control. It is also possible that some users don't like the autosave because they want to save when they feel their text is ready enough.
From what we observed, auto-saving is useful in this context. Users are still in control about when to publish the translation and auto-saving just makes their work resistant to data loss due to connection issues or leaving the page. The issues we found seem to be produced by either bugs or miscommunication of expectations (not noticing the content was saved).
Users can also trigger saving with the usual "ctr+s" shortcut, but exposing save as a top-level "save" action will require users to keep the boring task of saving regularly in mind and not getting confused with publishing (which could cause problems if it happens).