- From: Matt Reynolds <notifications@github.com>
- Date: Thu, 16 Jul 2020 15:48:22 -0700
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 16 July 2020 22:48:34 UTC
@nondebug commented on this pull request. > + as user gestures. A transition MUST NOT be included if the transition + could occur without user interaction. + </p> + <p> + The user agent MUST NOT expose information about connected gamepads + until a gamepad user gesture has been received from any connected + gamepad. The user gesture MUST be tracked independently for each gamepad + context. A <dfn data-lt="gamepad context">gamepad context</dfn> MUST be + created when a page first requests the current gamepad state or + registers for gamepad connection events. The gamepad context MUST be + destroyed when the tab is closed or navigates away from the current + page. Reloading the current page MUST NOT destroy the gamepad context. + </p> + <p> + To register a user gesture, a gamepad context MUST be active. A gamepad + context is active if the page associated with the context is visible and Do I need to add a reference to the spec somewhere else? These are getting red squiggly underlines. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/pull/136#discussion_r456120348
Received on Thursday, 16 July 2020 22:48:34 UTC