github.com/w3ctag/design-pri… makes it seem the @w3ctag is effectively a proxy for implementers rather than a body trying to figure out the best for the web.
2
2
Replying to @annevk @w3ctag
I don't think it's useful to give advice we know people aren't going to follow. The first step is the work of building enough consensus around restricting all features to secure contexts as a lever to move to TLS. Declaring it without enough momentum behind it doesn't help.

Apr 7, 2018 · 12:20 AM UTC

1
3
Replying to @davidbaron @w3ctag
Sure, but completely deferring to contemporary positions of browsers is weak sauce. It is possible to figure out a more coherent architectural position.
1