Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UX for errors caused by Lighthouse is unclear #9968

Open
connorjclark opened this issue Nov 13, 2019 · 3 comments
Open

UX for errors caused by Lighthouse is unclear #9968

connorjclark opened this issue Nov 13, 2019 · 3 comments

Comments

@connorjclark
Copy link
Collaborator

image
image

Two things here:

  1. It's not evident that ? means that we (Lighthouse) has errored, and the page is perhaps not at fault
  2. The error message is hidden behind a hover tooltip. This means screenshots don't have this super important message, and users reasonably wouldn't know to hover to see more

Suggestion for 1: In the category header, show an error message explaining that an audit in this category has errored due to an issue with running lighthouse, perhaps with a CTA to report a bug report.

Suggestion for 2: Could be the same solution, the error message could be in the header of the category. Would specify which gatherer it came from and the audits it affects. This would also help dedupe the same Error message we show now across all audits, even though they are usually the same error.

@patrickhulce
Copy link
Collaborator

Other issue: the error icon for an audit has the same icon on the left of the audit that a regular failing audit has.

@patrickhulce
Copy link
Collaborator

Potential action item: move the error message out from the tooltip and autoexpand it

@paulirish
Copy link
Member

Action items:

  • move the error message out from the tooltip and autoexpand it
  • change the error icon to not be identical to failing audit icon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants