Make WordPress Core

Opened 3 years ago

Last modified 3 weeks ago

#50402 accepted defect (bug)

Admin notices: error messages should not be all bold

Reported by: afercia's profile afercia Owned by: joedolson's profile joedolson
Milestone: 6.5 Priority: normal
Severity: normal Version:
Component: Administration Keywords: has-patch
Focuses: ui Cc:


Splitting this out from #47656.

While there are cases where the admin notices error messages may legitimately use bold form some terms within the message, the whole message shouldn't be bold.

The vast majority of the error admin notices are just text with a normal font weight. The <strong> element does add semantic (strong) emphasis but that's an addition that brings in very little vale. Visually: the bold message is inconsistent with most of the error admin notices.

Some examples:

echo '<div class="error"><p><strong>' . __( 'You cannot install a network of sites with your server address.' ) . '</p></div>';


echo '<div class="error"><p><strong>' . __( 'The network could not be created.' ) . '</strong></p>';

These "all bold" admin notices should be adjusted to remove the all-bold effect.

Worth also reminding the CSS class class="error" is legacy and should be replaced with class="notice notice-error".

Change History (5)

#1 @ocean90
3 years ago

Related: #37280

This ticket was mentioned in Slack in #design by afercia. View the logs.

3 years ago

#3 @joedolson
6 weeks ago

  • Milestone changed from Awaiting Review to 6.5
  • Owner set to joedolson
  • Status changed from new to accepted

This ticket was mentioned in PR #5651 on WordPress/wordpress-develop by @rajinsharwar.

3 weeks ago

  • Keywords has-patch added

Adding Bold only on the "Error:" text.

Trac ticket:

#5 @rajinsharwar
3 weeks ago

As for the current trunk, I found two instances of such inconsistency. I tried to review each instance of the Error: text and make them under the STRONG, and the remaining notice message as normal text. Let me know if any other instance where this was missed.

Note: See TracTickets for help on using tickets.