3 ms·
Firefox seems to have already implemented it behind prefs in Fx69 [0], and are just now waiting to toggle them to default true, presumably around the same time
by KwanEsq 7y ago
Firefox seems to have already implemented it behind prefs in Fx69 [0], and are just now waiting to toggle them to default true, presumably around the same time Chrome ships it, February 2020.
[0] https://groups.google.com/d/msg/mozilla.dev.platform/nx2uP0CzA9k/BNVPWDHsAQAJ https://groups.google.com/d/msg/mozilla.dev.platform/nx2uP0C...
- danShumway 7y agoThanks for the heads up, I was curious what Firefox's status was. I think that's just a smart move in general. There's certainly no PR reason to preemptively turn this setting on, it's better to see what happens when Chrome does. If it turns out to be a disaster, you delay, if not, you flip the switch a few days later so you're not lagging behind on security. Again, I have a reasonable amount of respect for the amount of publicity that the Chromium team has done here, because I think that if things go wrong, they're the ones who will be blamed by most people. It's good to bring up that Mozilla and Microsoft are also on board with this. It's not Google going off and doing something on their own or forcing the change despite objections, pretty much everyone including Mozilla seems to agree, and would like to see this change.