Last modified: 2013-03-04 19:38:57 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T47541, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 45541 - [TUX] Add feedback indication for proofread action
[TUX] Add feedback indication for proofread action
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
master
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-28 10:59 UTC by Pau Giner
Modified: 2013-03-04 19:38 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Pau Giner 2013-02-28 10:59:26 UTC
When the user marks a message as proofread, the change will be more clear if there is feedback to confirm that the translation was proofread.

We can achieve this by making a "proofread" text appear next to the proofread mark, similar to the text that is shown when hovering the edit icon, but shown when the proofread action is triggered and make it vanish after some seconds.
Comment 1 Siebrand Mazeland 2013-03-04 18:36:28 UTC
Please correct me if I'm wrong, but currently we indicate this by changing a" grey" check mark indicating "not proofread, but can be proofread by the current user" to a "black" check mark once the user has marked the unit as proofread.

There is a need for more visual feedback than that.
Comment 2 Pau Giner 2013-03-04 18:51:08 UTC
The issue was observed in a very early stage of the implementation when other issues were also contributing to the unclarity of status changes (e.g., lack of responsiveness in marker behaviour).

I think that status changes are now clear, but we may reconsider the feature  later if we still find problems.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links