You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the 500 error pages, all the text follows the same formatting, and there's also a clickable text with a link. However, it's often unclear that the text is actually clickable. To ensure clarity, it would be beneficial to establish a clear distinction between regular text and clickable text.
Describe the solution you would like
Would love to see a distinction between the regular and clickable text on the 500 error pages. On first look I was unsure it was clickable text or just normal text until I hovered the mouse over the text.
Describe alternatives you have considered
One effective approach could be assigning different font colors or font weights to these two types of text. This distinction in appearance would significantly improve the user experience and help users easily identify and interact with the relevant links.
Screenshots
Are there opened related issues?
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
On the 500 error pages, all the text follows the same formatting, and there's also a clickable text with a link. However, it's often unclear that the text is actually clickable. To ensure clarity, it would be beneficial to establish a clear distinction between regular text and clickable text.
Describe the solution you would like
Would love to see a distinction between the regular and clickable text on the 500 error pages. On first look I was unsure it was clickable text or just normal text until I hovered the mouse over the text.
Describe alternatives you have considered
One effective approach could be assigning different font colors or font weights to these two types of text. This distinction in appearance would significantly improve the user experience and help users easily identify and interact with the relevant links.
Screenshots
Are there opened related issues?
No response
The text was updated successfully, but these errors were encountered: