-
Notifications
You must be signed in to change notification settings - Fork 12
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
New default coloring #32
Comments
Agreed, I like your gray version.
Agreed, a red line feels more "Firefox-like".
Agreed, TLSv1.2 should be yellow now to push TLSv1.3.
Yes, let's make them red, they should not be used any more.
SSLv3 is disabled by default, I'm not sure if support for it was entirely removed in Firefox (e.g. what happens if you set
Agreed. |
Confirmed that it does not exist in latest Nightly by SSLLabs, so unless you want to support old Pale Moon or something, you can remove this 😁
Could you revise and revert this commit then? |
Well, if we did a solid gray color, it could blend in too much depending on the theme (maybe even the official dark one). Perhaps a white border around would help? |
Actually, why does it matter? As long as the numbers themselves are readable, it doesn't matter if the background is. Because deemphasis was the point. |
Sure, that would make sense. You could even use the original cross by taking it from the SVG
I thought #19 is sufficient, but yes, you can add a tooltip. |
Just updated the icons.
For some reason the triangle is not displayed in the current version, will investigate. |
Fixed it. Thank you @Madis0! 🚀 I will test it further and release it tonight. |
Indeed, I think matching other icons colors would be nicer. So lighter background and dark text. |
As TLS 1.0 and 1.1 are getting disabled (someday), it is time to consider new colors to use to better highlight the differences.
Ideally, perfect security must be transparent, therefore I suggest using the same gray color for 1.3 as Firefox itself uses for the padlock (black with opacity 0.6).
Mixed protocols could perhaps use an icon crossed with a red line, similar to the broken padlock).
A simple line should obstruct the number less than the previous warning triangle.
Could 1.2 be yellow now? It's not specifically bad until proven that a site uses insecure ciphers and it is still a recommended default. Maybe use a cross for bad configurations and 1.3 coloring for the rest?
1.0 and 1.1 should be bright red while they still exist, but is that enough?
Wait, why is SSL 3 still in this extension?
Unknown icon could be inverted, as it doesn't give much info anyway.
The text was updated successfully, but these errors were encountered: