Deprecating Non-Secure HTTP

After a robust discussion on our community mailing list, Mozilla is committing to focus new development efforts on the secure web, and start removing capabilities from the non-secure web.  There are two broad elements of this plan:

1. Setting a date after which all new features will be available only to secure websites
2. Gradually phasing out access to browser features for non-secure websites, especially features that pose risks to users’ security and privacy.
   

The second element of the plan will need to be driven by trade-offs between security and web compatibility.  Removing features from the non-secure web will likely cause some sites to break.