The only one that has major implementation changes is the Public Class Fields proposal, which has positive public signals from other browsers: Proposal - https

The only one that has major implementation changes is the Public Class Fields proposal, which has positive public signals from other browsers: Proposal - https://github.com/tc39/proposal-class-fields https://github.com/tc39/proposal-class-fields Firefox Implementation Tracker - https://bugzilla.mozilla.org/show_bug.cgi?id=1499448 https://bugzilla.mozilla.org/show_bug.cgi?id=1499448 Safari Implementation Tracker - https://bugs.webkit.org/show_bug.cgi?id=174212 https://bugs.webkit.org/show_bug.cgi?id=174212 The others are largely security updates which honestly I'm fine with browsers pushing ahead with. The User activation query API stuff is great and is gonna solve a lot of headaches around misbehaving sites. Safari already has a rudimentary implementation around this with autoplay as well, so this is an effort to standardise some existing "monoculture bullshit". As far as depreciating TLS 1 and 1.1, I don't think there's anyone out there arguing that that isn't a good idea.