Consider making "gamepadconnected" part of “activation triggering user event”? about html

[pshaughn]

Given the gamepad specification: "A user agent MUST dispatch this event type to indicate the user has connected a gamepad. If a gamepad was already connected when the page was loaded, the gamepadconnected event SHOULD be dispatched when the user presses a button or moves an axis." I feel like some gamepadconnected events are candidates for user activation, and some aren't.

If I've just coincidentally plugged in a gamepad or had a Bluetooth connection dropout/dropin while the page is open, or if I have a rotation-sensing gamepad I've just moved a little on my desk, I wouldn't want that to be activation... but if I'm pressing a button, or I'm pushing a shoulder trigger axis all the way from one extreme to the other, then I'd probably like that to be activation. I'm thinking maybe something like connection no, button yes, axis leave up to implementors.