Last modified: 2014-04-04 14:32:11 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 T64304, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 62304 - Start cancel button as quiet neutral, but change to quiet destructive when there are changes
Start cancel button as quiet neutral, but change to quiet destructive when th...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
1.23.0
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-06 04:44 UTC by Matthew Flaschen
Modified: 2014-04-04 14:32 UTC (History)
5 users (show)

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


Attachments

Description Matthew Flaschen 2014-03-06 04:44:11 UTC
In either case, there is no visible color when the user is not hovering, so this should not be too attention-grabbing.

However, with destructive, it will highlight red when they hover, to reinforce that they will lose their unsaved changes.

We might also want to change the text to 'Discard changes' at that point, although that might be overly attention-grabbing (not sure).

See thread on design list starting at http://lists.wikimedia.org/pipermail/design/2014-March/001588.html , and related Flow bug 62290.

See also in progress change to the edit form (https://gerrit.wikimedia.org/r/#/c/116725/), which will probably do the quiet part of this, but not necessarily the destructive on change.

We should update the style guide if this is implemented.
Comment 1 Matthew Flaschen 2014-03-07 07:34:53 UTC
(In reply to Matthew Flaschen from comment #0)
> We might also want to change the text to 'Discard changes' at that point,
> although that might be overly attention-grabbing (not sure).

See Pau's followup (http://lists.wikimedia.org/pipermail/design/2014-March/001605.html).  They've done some experiments (not exactly this text, but similar concepts) that indicate such changes are useful, which supports doing it here.

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


Navigation
Links