-
Notifications
You must be signed in to change notification settings - Fork 287
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
[BUG] Make sure if the HTTPS tests are timing out that the message is clear to the user #4723
Comments
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
22 similar comments
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
What happened?
When HTTPS tests timeout they just show as failure to the user which can be confusing.
How do we reproduce the behavior?
I'll just paste a screenshot.
What do you expect to happen?
If its timing out, it should say that and maybe point to what that can do to help speed up their load times or something like that.
What environment were you using?
Windows 11 latest
Edge latest
Additional context
No response
The text was updated successfully, but these errors were encountered: