Update TLS warning steps for different browsers #4991
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
I noticed that on Safari the instructions were for Chrome, and I noticed that the wording for the instructions were out of date for several browsers.
In addition to fixing those things, I added support for Edge (I think many enterprises use Windows) and Opera because they were easy. But I didn't have images for those, so I don't show an image for those.
We also showed Chrome instructions if we didn't recognize the browser, so I added some default text that would show in unhandled browsers
Unhandled:
Edge with no image:
Firefox with image:
Which issue(s) this PR fixes:
Does this PR require a test?
NONE
Does this PR require a release note?
Does this PR require documentation?
NONE