On Fri, Apr 28, 2017 at 7:10 PM, Eric Rescorla <e...@rtfm.com> wrote: > Rather, the policy is > that we will move to requiring all new features to have HTTPS [0].
We should probably discuss that again at some point, since it's not meaningfully enforced and I don't think it has consensus within Mozilla either. It's also very much unclear what the scope of it is, whether a new CSS property should get that treatment, a new method on Node, etc. > [0] > https://blog.mozilla.org/security/2015/04/30/deprecating-non-secure-http/ -- https://annevankesteren.nl/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
