-
-
Notifications
You must be signed in to change notification settings - Fork 929
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
Use HTTPS links where applicable. #2311
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great!
no-browser-hacks
and no-indistinguishable-colors
are deprecated. It won't hurt to change links in their descriptions, though :)
@@ -1,6 +1,6 @@ | |||
# no-invalid-double-slash-comments | |||
|
|||
Disallow double-slash comments (`//...`) which are not supported by CSS and [could lead to unexpected results](http://stackoverflow.com/a/20192639/130652). | |||
Disallow double-slash comments (`//...`) which are not supported by CSS and [could lead to unexpected results](https://stackoverflow.com/a/20192639/130652). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Funny thing: it redirects to HTTP. Shall we use the final URL instead? https://stackoverflow.com/questions/12298890/is-it-bad-practice-to-comment-out-single-lines-of-css-with/20192639#20192639
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ha, it does to, I use the HTTPS Everywhere Chrome extension from EFF.
And for me, it remains on the HTTPS site, so either or I guess
I've a preference to make as many as possible links used HTTPS
LGTM |
Maybe also a future a beginner-friendly PR could be accepted that updates our code examples to prefer when possible the use of
https://
in our code examples.