https://github.com/w3ctag/design-principles/pull/89 … makes it seem the @w3ctag is effectively a proxy for implementers rather than a body trying to figure out the best for the web.
I suggestted a different tack, as I view @w3ctag as valuable only to the extent it provides actionable advice. Having nothing in guidance (previous status quo) served nobody. New advice warns feature developers of (evident) difficulty in not adopting Secure Contexts.
-
-
The debate had been going in circles, and as the
@w3ctag has no power to compell any UA or feature designer to do anything, providing advice that is *likely* to result in more Secure Contexts features with less drama seemed to unstick us. -
We have been asking designers to consider adopting Secure Contexts for some time and advocate for an E2E encrypted web. Making toothless demands, however, is hardly an effective way to reach the goal we all share.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.