-
Notifications
You must be signed in to change notification settings - Fork 77
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
Firefox: Permission denied to access property "type" #96
Comments
Thanks @candymac. What version are you using? |
Thanks for quick reply. Looks like we're on v5.2.1 - I see there have been a few subsequent updates. |
There has, but the line you're referring to does still exist here https://github.com/ten1seven/what-input/blob/master/src/scripts/what-input.js#L244 However, some of the updates had to do with mouse event handling. Would you be up for testing out the current version to see if the issue is still there? If so, I'm happy to dig into it. Is your app public facing if I were to pull it up in Firefox for FireTV for testing? |
We went ahead and upgraded. I'll circle back in the next week and let you know if the reports persist. Also, I haven't independently verified the issues on FireTV... I'll do so first, to try to rule out any issues with our code. Stay Tuned. |
FireTV "stay tuned" 🥁 |
Hi, just wanted to follow up. So it appears the FireTV issue was unrelated to what-input, but thanks for offer to test it out. We do however continue to get the same report sporadically on Sentry after upgrading ... we've been unable to reproduce it ourselves and unclear what conditions might cause it to occur, or if it even adversely effects functionality. |
also seeing the same issue with 5.2.3 and Firefox |
Sentry has been reporting an issue specific to Firefox: Permission denied to access property "type" on line 296 of dist/what-input.js - it is specific to Firefox across various platforms but seems intermittent.
Also thought I'd mention some users on Firefox for FireTV are reporting an issue that seems to be consistent with the browser reporting 'mouse' as the current input device, but this might not be related (or perhaps though not technically a mouse this is correct, though it breaks some functionality in our case).
The text was updated successfully, but these errors were encountered: