- From: Miniontoby <notifications@github.com>
- Date: Wed, 01 Mar 2023 01:58:27 -0800
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 1 March 2023 09:58:41 UTC
> > I think [https://wicg.github.io/local-network-access/](local-network-access) (if the community gets agreement and it gets standardized) will solve for this. If I understand that spec correctly, it will allow for local things to be treated as "secure context". > > I don't think that is what this proposal suggests. Yeah partly it is not that. I just don't see in how requesting/getting access to the current connected gamepads would be usefull for 'hackers' to do malisious things. I understand camera and microphone would have to be secure context, but this, this just doesn't make sense. But maybe the local network access would be the solution for me if this really is being forced into, but else please rethink your idea of making this function secure context only. Btw the `ongamepadconnected` event doesn't seem to be removed for non secure context (or at least it doesn't give message and it doesn't seem to be changed in the PR) with this and still gives you access to the connected gamepad, but because chrome just saves a snapshot so you cannot do very much with it. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/issues/113#issuecomment-1449746934 You are receiving this because you are subscribed to this thread. Message ID: <w3c/gamepad/issues/113/1449746934@github.com>
Received on Wednesday, 1 March 2023 09:58:41 UTC