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

Thanks for your prompt reply, Marcos.

> The Web App Sec working group need to figure this out, to be honest... particularly as part of:
https://github.com/w3c/webappsec-secure-contexts


Great to see that there's a working specification for these types of issues. Thanks for linking this.

> No. That would be really bad. Definitely we don't want to train users to navigate around those warnings.

Sorry, I might have jumped the gun a bit here. My aim was more to ask what the recourse is for local projects wanting to use secure context APIs. The only real path forward I’m seeing is passing certificate management onto the user for local situations? If so, this will be a challenging task for a some people. I realize, though, that use-cases like the project I maintain and the original thread starter are likely in the minority for how the Gampad API gets used, on average. Still, this move is a bit disappointing to see, from my perspective.

No matter, I’ll look forward to development in the specification you linked, going forward.

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