-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gamepad support broken on all browsers now? #131
Comments
rip 😔 |
Turning this into an online-hosted Progressive Web App that works offline by adding an appropriate Service Worker is probably also an option. You could host it for free on Netlify (or similar). |
why not just supporting using custom ssl certificates? |
I haven't looked into it until now. The main annoyance is getting your CA for 192.168.43.1/192.168.49.1 trusted by the system. Maybe we can get by with this approach? I might try it out if I get the chance. |
Oh never mind, I guess we have advanced the target SDK! I guess we moved past 19 after my time in the program. |
You have to get the client to trust it. It doesn't matter if the host device does or doesn't as long as the webserver supports it. |
Oh duh, thanks for correcting me
…On Thu, Feb 23, 2023, 1:07 PM jpdagostino ***@***.***> wrote:
You have to get the client to trust it. It doesn't matter if the host
device does or doesn't as long as the webserver supports it.
—
Reply to this email directly, view it on GitHub
<#131 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABS6GQSNPHS5NZXEATINEVTWY7GR7ANCNFSM6AAAAAAU5O3BJI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
The problem was that our gamepad was not on the supported gamepad list. After adding support for it, it worked fine on localhost and 192.168.43.1.
When we tried hosting on a website (https://ftcdash-pwa.vercel.app/dash) to use it as a PWA, we could not connect the WebSocket. Apparently, to make a websocket connection, both sides have to use HTTP or both have to use HTTPS, but to access the gamepad on firefox, you need the website to be on HTTPS (it works fine on chromium over HTTP). So now we are just using FTC-Dash hosted on the robot controller and accessed through Chromium.
I tried it on Chromium (the open source one) Version 108.0.5359.71 (Official Build) (64-bit) on Linux (NixOS) and was able to access the gamepad without HTTPS |
Any way custom certificates could be supported? https://github.com/FiloSottile/mkcert was happy to generate them for 192.168.43.1 and Firefox on my laptop accepts them, I'm just not sure where to start to get them used by the robot. |
Since the IP address is basically always going to be the same, the same cert could be used by all robots. |
I also managed to get the Tauri version working like Noah suggested: https://github.com/jdhs-ftc/ftc-dashboard |
https://chromestatus.com/feature/5138714634223616
Looks like Secure Context is also required on Chrome now. It looks like local HTTPS support is needed to bring back Gamepad support to all browsers.
The text was updated successfully, but these errors were encountered: