[wp-trac] [WordPress Trac] #47656: Remove 'Error:' prefixes from error notices as they're redundant
WordPress Trac
noreply at wordpress.org
Tue Jun 16 15:13:01 UTC 2020
#47656: Remove 'Error:' prefixes from error notices as they're redundant
-------------------------+-------------------------------------------------
Reporter: garrett- | Owner: audrasjb
eclipse |
Type: enhancement | Status: assigned
Priority: normal | Milestone: 5.5
Component: I18N | Version:
Severity: normal | Resolution:
Keywords: has-patch | Focuses: ui, accessibility, administration,
commit | ui-copy
-------------------------+-------------------------------------------------
Comment (by afercia):
To better clarify the point that the message ''content'' is more important
than the "Error" prefix, here's a summary of some bits of
[https://wordpress.slack.com/archives/C02RP4X03/p1580483849221400 the
relevant conversation on the WordPress Slack].
For example, when the "Error" prefix is in a `wp_die()`:
[[Image(http://cldup.com/iqCFMVAUTs.png)]]
> On such a page, it’s pretty evident an error occurred. I'm not sure what
value the word “Error” adds in this case.
Same applies to the admin notices: they're already pretty prominent.
> When the content is clear and understandable by everyone, there's
probably no need to add anything else.
Also regarding consistency: in the current WordPress codebase, there are
error messages that don’t use the prefix “Error” at all. Overall, keeping
it simple is probably the best option.
Lastly, reading the arguments from #15887, I'm not sure "yelling" at users
is a good strategy for a good user interface.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47656#comment:28>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list