Re: [w3c/gamepad] Proposal for the Gamepad Interop 2027 (Issue #231)

xingri left a comment (w3c/gamepad#231)

updated proposal by updating the feedbacks on the August WG discussion.
  - Reworked virtual gamepad input from gamepad.update() into a gamepad source for test_driver.Actions.
  - Kept connect() and disconnect() as separate lifecycle APIs.
  - Added richer virtual-device descriptors: context, axis bounds, button types/bounds, touch surfaces, and vibration capabilities.
  - Added Actions support for axis input, buttons, independent pressed/touched, and touch contacts.
  - Updated WebKit and Chromium implementation paths, diagrams, checklist, cleanup, and error behavior for the Actions design.
  - Added an Actions-vs-update() comparison, with browser-specific pros and cons for WebKit and Chromium.
  - Added GamepadButton.type coverage using virtual buttons typed as "standard", "non-standard", and "trackpad".
  - Added planned tests for IDL, type values/order, input-state independence, and standard-mapping behavior.
  - Clarified that button-type tests remain tentative and feature-gated with assert_implements_optional until the API is standardized and implemented.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/231#issuecomment-5614614811
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/gamepad/issues/231/5614614811@github.com>