On Fri, Feb 2, 2018 at 2:45 PM, Tom Schuster <t...@schuster.me> wrote:
> Any additional ideas how to mitigate the risk here? Chrome seems to
> want to add a kill pref for this, from my experience more difficult
> for us with the way we define methods in SpiderMonkey. Should that be
> a requirement for shipping?
Don't we need that type of availability mechanism to support
HTTPS-everywhere anyway? "All new features..."
dev-platform mailing list