Last modified: 2014-11-20 23:58:50 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 T75679, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 73679 - Flow: Preview message looks like an error and has question mark cursor
Flow: Preview message looks like an error and has question mark cursor
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: design
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-20 23:58 UTC by Krinkle
Modified: 2014-11-20 23:58 UTC (History)
5 users (show)

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


Attachments
Screenshot of preview warning (89.82 KB, image/png)
2014-11-20 23:58 UTC, Krinkle
Details

Description Krinkle 2014-11-20 23:58:50 UTC
Created attachment 17184 [details]
Screenshot of preview warning

The preview indication triggered after pressing "Preview" in the reply editor looks like a warning or error. And the warning doesn't look like other MediaWiki warnings (class=errorbox). It also doens't look like what a warning would look like within the UI style that Flow itself uses. It's implemented as a lost paragraph with a custom text color.

It also has a custom cursor style (see screenshot) which is in my opinion confusing. The 'help' cursor is generally used for when hovering or clicking there will reveal additional information (e.g. definition, explanatory tooltip, or guidance popup). But in this case it probably was meant to communicate this is "helpful" text, but the text itself should make that clear. A regular text (default) or pointer cursor is probably better fitted.

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


Navigation
Links