Skip to content

Way to surface non-critical errors in the report #1512

@ebidel

Description

@ebidel

From #1492 (review)

For individual gatherers/audit errors, we surface debugString.

Right now, fatal errors stop the extension from running and we show a "report error" button. However, for non-fatal errors that happen outside of the gatherer -> audit -> report pipeline, we don't have a way to surface those errors to extension users.

Without analytics, we don't know about non-fatal errors. The HTML report could have a section where users see overall LH non-fatal errors and file bugs against us.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions