WordPress.org

Make WordPress Core

Opened 19 months ago

Last modified 15 months ago

#47222 new defect (bug)

Site Health Check: UI glitch leads user to confuse recommended improvements with critical issues

Reported by: DavidAnderson Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 5.2
Component: Site Health Keywords: site-health has-patch
Focuses: ui Cc:

Description

I am looking at "Site Health Check" on a site with no critical issues.

In the UI, "0 Critical issues" appears briefly, and then a few seconds later disappears. This leaves "3 Recommended improvements". However, following the disappearance of "0 Critical issues", these recommended improvements are then preceded by text which suggests that they are themselves critical and require immediate action: "The site health check shows critical information about your WordPress configuration and items that require your attention."

See attached screenshots.

Attachments (5)

before.png (21.4 KB) - added by DavidAnderson 19 months ago.
Before the disappearance
a-few-seconds-later.png (16.6 KB) - added by DavidAnderson 19 months ago.
The ambiguous situation afterwards
Site Health Status ‹ Yoeri — WordPress.png (75.4 KB) - added by yoeridekker 18 months ago.
before
Site Health Status ‹ Yoeri — WordPress (1).png (104.3 KB) - added by yoeridekker 18 months ago.
After
47222.diff (4.1 KB) - added by palmiak 18 months ago.

Download all attachments as: .zip

Change History (12)

@DavidAnderson
19 months ago

Before the disappearance

@DavidAnderson
19 months ago

The ambiguous situation afterwards

#1 @SergeyBiryukov
19 months ago

  • Keywords site-health added

#2 @Hareesh Pillai
19 months ago

  • Focuses ui added
  • Keywords needs-patch added

#3 @yoeridekker
18 months ago

What about only removing the empty container and leaving the "0 Critical issues" there?

#4 @palmiak
18 months ago

That's true - that may be confusing. In my patch I've done two things:

  • I've added an extra description for the "Recommended improvements" - I'm not native english speaker so it may need some tweaking
  • I've tweaked the JS a bit so the headers are also hidden

@palmiak
18 months ago

#5 @msaggiorato
18 months ago

  • Keywords has-patch added; needs-patch removed

#6 @desrosj
18 months ago

  • Component changed from Administration to Site Health

Moving Site Health tickets into their lovely new home, the Site Health component.

#7 @Clorith
15 months ago

I have a counter proposal, as I agree this isn't the best UX right now, but I don't think adding more descriptions to go with the headers is the right solution;

Hide the sections (with headers) by default, until at least 1 check falls inside of it. This means there's no need to hide empty ones after the fact when all is done, and means less "janking" on the screen for the user observing.

Note: See TracTickets for help on using tickets.