My organization recently implemented a permissions policy disallowing gamepad. I am not including any of the gamepad input modules in our application; it is not something we are actively using. I tried disabling gamepad in the MapView using gamepad: false; however, the map chokes on load and the console reports an error.
Here's the error and call stack:
Uncaught DOMException: Failed to execute 'getGamepads' on 'Navigator': Access to the feature "gamepad" is disallowed by permissions policy.
at w._forEachGamepad (https://js.arcgis.com/4.27/esri/views/MapView.js:284:66)
at new z (https://js.arcgis.com/4.27/esri/views/MapView.js:281:154)
at new g (https://js.arcgis.com/4.27/esri/views/MapView.js:271:90)
at F._connect (https://js.arcgis.com/4.27/esri/views/MapView.js:236:292)
at https://js.arcgis.com/4.27/esri/views/MapView.js:236:48
at z (https://js.arcgis.com/4.27/:1717:105)
at G.notify (https://js.arcgis.com/4.27/:182:158)
at d (https://js.arcgis.com/4.27/:178:400)
at F.l [as callback] (https://js.arcgis.com/4.27/:179:7)
at d (https://js.arcgis.com/4.27/:187:15)
I can fix the issue by reverting the policy, but that is a last resort option for our organization. Any ideas on how to prevent the map from trying to call getGamepads?