This question already has an answer here:
- Network-wide HTTPS: It's time 40 answers
Every once in a while, someone comes to Meta to report a bug about something not working and it turns out that person is visiting one of the network sites over HTTPS/SSL. The problem has been growing since browsers started to outright block mixed content instead of showing a warning.
The usual answer is that HTTPS is not yet fully supported, and the person should try again using HTTP. Sometimes things get fixed, improving the situation a bit.
Is there a roadmap for full support? Partial support has been there for more than two years now.
Is this actively being worked on? If not, what are the reasons to partially support it instead of disabling it completely to avoid these problems?