Gamepad API - secure_context_required

[hamishwillee]

FF91 requires gamepad has secure context: https://bugzilla.mozilla.org/show_bug.cgi?id=1704005. Further, Chrome also puts gamepad in secure context from v86, though I read this as being behind a flag: https://bugs.chromium.org/p/chromium/issues/detail?id=1099544

This updates theMDN listed GamePad APIs:
Gamepad, GamepadButton, GamepadEvent, GamepadHapticActuator, GamepadPose.

I did a check on Navigator.getGamepads() and that also requires a secure context. Since not everything in Navigator does, do I need to do add secure_context_required as a subfeature of the method??
I can't tell if Window.ongamepadconnected event and disconnected would require secure context - I get null on both secure and insecure contexts.

Related docs work can be tracked in mdn/content#6723. This is associated with the change in #11770

[queengooborg]

If Navigator.getGamepads() also requires secure contexts, then yes, we should add secure_context_required as a subfeature to the method! (So we'll have a api.Navigator.getGamepads.secure_context_required feature.)

So far, this is LGTM!

[hamishwillee]

Thanks @vinyldarkscratch . I've added api.Navigator.getGamepads.secure_context_required along with the same thing for the connected/disconnected event handlers. Mirroring the other cases and setting as false if the parent is false.

I think this is now ready for re-review.

[queengooborg]

Thanks for the quick response, this looks all good to go now!