Page MenuHomePhabricator

FileAnnotations prototype 2: Floating green button is confusing and non-standard
Closed, DeclinedPublic

Description

https://prtksxna.github.io/wikimedia-prototypes/fileannotations/needs_annotation_category/category/category.html

Non-standard button. In the current context, the action to add an annotation seems clear. From the UI Standardisation perspective we need to consider that the shape (round) and the color (bright green) don't align with existing standards. So we may want to think how and when this new component is expected to be used in other cases.

@dchen says

i think the annotations 'state' needs to be more clearly trigger-able for users, and then everything will more clearly fall in place, and there can be more visual consistency... possibly blue buttons and green + icons won't even be necessary to have.

Event Timeline

See also T154752: FileAnnotations prototype: No indication on how to edit/undo the annotation that was just addded, it might need a floating button too. Discussion on how to attach an action to a card there.

In the case of an empty annotation, we could show an empty card with actions, instead of just a floating button on top of the image.

Floating buttonEmpty card
Screen Shot 2017-01-09 at 2.29.07 PM.png (149×221 px, 69 KB)
Screen Shot 2017-01-09 at 2.37.58 PM.png (152×378 px, 88 KB)

In the case of an empty annotation, we could show an empty card with actions, instead of just a floating button on top of the image.

Makes sense. However, we may want to communicate the fact that is empty in a less verbose and more visual form in order to suggest it is empty even before reading the text.

Ramsey-WMF changed the task status from Open to Stalled.Nov 17 2017, 5:14 PM
Ramsey-WMF lowered the priority of this task from Medium to Lowest.
Ramsey-WMF added a project: SDC General.
Ramsey-WMF subscribed.

Since the 2016/2017 FileAnnotations prototype work is now quite outdated and both Wikidata and Commons have new features and design plans (like moving new features to Vue.js on Commons), and the extension is not actively under development, the best thing to do is close these tasks and create new ones when/if there's a team available to pick up development on this feature.