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.
-
-
The TAG is half implementors (https://www.w3.org/2001/tag/ ), but 1) it's not clear from the notes which group weakened the advice, and 2) it's not clear that restricting, say, :focus-visible to secure contexts is any better for the web than the Semantic Web was.
1 reply 0 retweets 1 like -
1) Given what they ended up writing down it is perfectly clear. 2) Restricting features in aggregate will inevitably lead to HTTPS adoption. Comparing it to a no-op is disingenuous.
1 reply 0 retweets 0 likes -
1) Implementers and users were split in https://github.com/w3ctag/design-principles/pull/75 …. Outcome that reflects the split isn't just "acting as a proxy for implementers". 2) My point with the Semantic Web comparison is that it's good to pay attention to implementers. You agree, or you won't be at WHATWG.
2 replies 0 retweets 2 likes -
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.1 reply 0 retweets 0 likes -
Replying to @slightlylate @jyasskin and
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.1 reply 0 retweets 0 likes -
Replying to @slightlylate @jyasskin and
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 reply 0 retweets 0 likes
Nor is failing to warn feature designers of the political and practical risks of failing to adopt Secure Contexts.
Power abides with implementations (including FF). The @w3ctag has only moral authority, derived from our ability to assist feature designers on their journey.
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.