| • Jan_Dittrich | |
| May 9 2017, 12:44 PM |
| F8011279: image.png | |
| May 10 2017, 6:52 AM |
| F7998348: image.png | |
| May 9 2017, 3:52 PM |
| F7998277: Screenshot from 2017-05-09 17:39:52.png | |
| May 9 2017, 3:41 PM |
| F7995532: image.png | |
| May 9 2017, 12:52 PM |
| F7995556: image.png | |
| May 9 2017, 12:52 PM |
| F7995496: image.png | |
| May 9 2017, 12:46 PM |
Two issues with the attention icon:
we should investigate how/if both issues are actually problems and how we could solve those.
| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Resolved | • Jan_Dittrich | T164352 UI Design for Constraint Checks/Violations | ||
| Resolved | • Jan_Dittrich | T164831 Investigate Design of the Icon | ||
| · · · |
Assumption: Making the errors disappear is motivating, so giving an indicator how far one needs to go, maybe a nice thing.
The question we really need to answer is: do we need the number at all? I don't believe we do. It only adds more noise to the already noisy UI.
If in user tests it turns out we do need it then it shouldn't be visually disconnected but for example inside the triangle.
People are used to notifications with numbers--even if they don't need it, it's a bit of a surprise to open a little triangle of doom and find that your triangle is really 10 triangles (not that such a doom and gloom case is to be expected).
Related change: https://gerrit.wikimedia.org/r/#/c/352815/ (don’t show number of violations if it’s 1)
Change 352850 had a related patch set uploaded (by Lucas Werkmeister (WMDE); owner: Lucas Werkmeister (WMDE)):
[mediawiki/extensions/WikibaseQualityConstraints@master] Make constraint report button framed
Change 352850 makes the button framed, as shown in the last of the three buttons in the screenshot @Jan_Dittrich posted. Do you think that’s an improvement?
This is what the patch https://gerrit.wikimedia.org/r/352850 currently does:
Alternatively:
I just copied a few styles from the framed button and added them to the unframed one. It’s not as nice as just using what OO.ui gives us, but if it looks better…
There are different assumptions about what the feature does not not does and also what the actual problem is. For some it is a useful indicator, others see it as cluttering. Only way to find out is to test it.
If it is seen as really problematic to keep it, we can take it out. But: I see no big problems with keeping it the way it is regarding the number, and I think that "the indicator may look like text" and "people may not know that it is interactive" have actual scenarios of which problems and confusions they cause.
@Lucas_Werkmeister_WMDE, @thiemowmde : Yes, that is too massive. So, lets remove the border. Lets also sit together and find another way to indicate interactivity (maybe via hover styles, background or something else).
In the long run, I would like these items go to a place where people will know that stuff there is interactive. Like indicators for battery, sound, language etc. in your desktop bar
Change 352850 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Make constraint report button framed
It is not clear that it is interactive
"the indicator may look like text" and "people may not know that it is interactive" have actual scenarios of which problems and confusions they cause.
Do we know that this is an actual problem for users? Have we heard this complaint from them? As far as I’m aware, it’s just a potential concern from our side, and it might not be worth cluttering the interface to fix it when it’s not a problem people actually have.
Change 353023 had a related patch set uploaded (by Lucas Werkmeister (WMDE); owner: Lucas Werkmeister (WMDE)):
[mediawiki/extensions/WikibaseQualityConstraints@master] Un-frame report button and remove number
Change 353023 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Un-frame report button and remove number
