* Add paragraph about browser add-ons when encountering some errors
When a crash is caused by a NotFoundError exception, add a paragraph
to the error page mentioning browser add-ons.
Indeed, crashes with NotFoundError are often caused by browser extensions
messing with the DOM in ways React.JS can't recover from (e.g. issues #13325
and #14731).
* Reword error messages
<pclassName='error-boundary__error'><FormattedMessageid='error.unexpected_crash.explanation'defaultMessage='Due to a bug in our code or a browser compatibility issue, this page could not be displayed correctly.'/></p>
<pclassName='error-boundary__error'>
<p><FormattedMessageid='error.unexpected_crash.next_steps'defaultMessage='Try refreshing the page. If that does not help, you may still be able to use Mastodon through a different browser or native app.'/></p>
{likelyBrowserAddonIssue?(
<FormattedMessageid='error.unexpected_crash.explanation_addons'defaultMessage='This page could not be displayed correctly. This error is likely caused by a browser add-on or automatic translation tools.'/>
):(
<FormattedMessageid='error.unexpected_crash.explanation'defaultMessage='Due to a bug in our code or a browser compatibility issue, this page could not be displayed correctly.'/>
)}
</p>
<p>
{likelyBrowserAddonIssue?(
<FormattedMessageid='error.unexpected_crash.next_steps_addons'defaultMessage='Try disabling them and refreshing the page. If that does not help, you may still be able to use Mastodon through a different browser or native app.'/>
):(
<FormattedMessageid='error.unexpected_crash.next_steps'defaultMessage='Try refreshing the page. If that does not help, you may still be able to use Mastodon through a different browser or native app.'/>