Re: [w3c/gamepad] Please don't restrict to a secure context (#145)

> I'd at least like to have a statement from the W3C as to _why_ we're seemingly getting ignored

Please note that the W3C as an organization rarely unilaterally decides to make changes to APIs. Ultimately it is implementations who make changes and the W3C provides a forum for coordinating their work. The W3C Technical Architecture Group provides [design guidance for when a secure context is required](https://www.w3.org/TR/design-principles/#secure-context) but recognizes that there is disagreement on how broadly this should be applied.

At the moment it appears that only Firefox has shipped this change. Safari and Chrome have shipped warnings about the future deprecation. I can't speak for Safari but @nondebug's comment above shows how Chrome is thinking about reducing the impact of this change. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/145#issuecomment-1560153387
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/gamepad/issues/145/1560153387@github.com>

Received on Tuesday, 23 May 2023 21:37:01 UTC