input-device-capabilities
input-device-capabilities copied to clipboard
WICG
InputDevice API proposal
From discussion of @bmathwig's [DeviceId proposal](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/PointerEventDeviceId/explainer.md) on [blink-dev](https://groups.google.com/a/chromium.org/g/blink-dev/c/_s7rj-CuMF8/m/F34UOxw-AgAJ) and in https://github.com/w3c/pointerevents/issues/353 Consider adding a boolean or enum which indicates where `PointerEvent#pointerId` is coupled to a particular hardware device.
This spec hasn't moved in a few years.... should we consider incubation complete and archive this repo? @RByers?
I skimmed through #26 and the linked discussions but they seem to be focusing _(har har)_ on displaying different styling based on keyboard vs mouse. #39 might also be relevant...
An event to detect the capabilities of a pointer device have changed when the user switches between devices. Consider a Touchscreen laptop with pen support, a mouse and a trackpad;...
Suggests that a `firesHoverEvents` boolean is added to allow accurate handling of different pointer-based input devices. There are a number of benefits that this allows for by allowing to changing...
Similar to issue [Suggest adding a firesHoverEvents property](https://github.com/WICG/input-device-capabilities/issues/39) Suggests that a property `isCoarse` boolean is added to allow accurate handling of different pointer-based input devices. There are a number of...
This is an automated pull request to align the spec with the latest Web IDL specification. Currently the autofix might introduce some awkward code formatting, so please feel free to...
From the beginning of [the brainstorming](https://docs.google.com/document/d/1WLadG2dn4vlCewOmUtUEoRsThiptC7Ox28CRmYUn8Uw/edit#) for this API there was discussion about eventually supporting device enumeration. It looks like we didn't have a GitHub issue to track that though....
There are tests in https://github.com/WICG/InputDeviceCapabilities/tree/gh-pages/tests The string "firesTouchEvents", "pointerMovementScrolls" and "sourceCapabilities" never appear in wpt, so there probably aren't any tests there. Picking a directory name will be fun, see...
Would it make sense to indicate in the InputDeviceCapabilities for mouse that the primary and secondary buttons are swapped? You can do this via querying GetSystemMetrics(SM_SWAPBUTTON) on Windows. The only...
