After (or as part of) T104419: Convert Special:MassMessage to use OOUI, consider setting the "Send" button color to red. Even small mistakes can make such a mess.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Goal | None | T122014 Convert all extensions/skins to OOUI | ||
| Open | None | T49145 Formally deprecate jQuery UI after we've stopped using jQuery UI in extensions and core | |||
| Resolved | TheDJ | T187992 Convert MediaWiki extensions WikiLove and MassMessage to use OOUI | |||
| Resolved | Dreamy_Jazz | T104419 Convert Special:MassMessage to use OOUI | |||
| Declined | None | T191171 After OOUI-ification, consider setting the Send button color to red |
Event Timeline
Comment Actions
Thinking T104419 is a blocker? Maybe this can be picked up after the blocker is complete? or could even be done along-side?
Comment Actions
It shouldn't be a red (“Red50“ or destructive) button. If this is such a problem, a notice above (better) or a warning dialog (not so good, as it might cover important other UI) should be considered. A destructive flagged button should only be used in contexts where removing data/data loss is happening.
Comment Actions
Generally, I usually notice "Blue" or "Default" as button for some action apart from delete. Yes I agree the "red" is indicates some form of removal so in this case, maybe "blue" does the trick? What about preview, maybe it can maintain the default color? So;
Send => "Blue"
Preview => "Default"
Does that make sense?
Comment Actions
@D3r1ck01 Would you mind adding a screenshot of current status for better understanding?
Comment Actions
A red button is not the right approach, if necessary I'd rather put a notice message atop of the button (even though that's sounds like a bad user-interface as well form first look on).