CX landing screen and selector looks disabled, grayed out, causing people to think it is all disabled and no actions available
The buttons become enable only when user start typing. But there must be someway to make it looking "inviting"
santhosh | |
Feb 25 2015, 3:41 PM |
F47042: pasted_file | |
Feb 25 2015, 3:52 PM |
CX landing screen and selector looks disabled, grayed out, causing people to think it is all disabled and no actions available
The buttons become enable only when user start typing. But there must be someway to make it looking "inviting"
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Focus the source title input when opening the selector | mediawiki/extensions/ContentTranslation | master | +2 -0 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T76456 Language Engineering tracker of trackers (tracking) | |||
Resolved | Arrbee | T87162 [Tracker] CX Phase 1 deployment issues | |||
Resolved | Pginer-WMF | T90727 CX landing screen and selector looks disabled, grayed out |
In order to better illustrate what to do next, we should make the input focus move to the search field.
I can think on other design improvements, but making the button enabled does not seem to improve the situation too much since we cannot start a translation if the user does not provide an article. That would turn the "button is disabled" problem into a worse "the button does not work" problem.
Change 192989 had a related patch set uploaded (by Amire80):
Focus the source title input when opening the selector
Change 192989 merged by jenkins-bot:
Focus the source title input when opening the selector