WICG input-device-capabilities issues

WICG / input-device-capabilities

InputDevice API proposal

MIT License

17 stars 14 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Consider a hasDeterministicPointerId capability

#43 RByers opened 1 year ago
1
Focus events and keyboard navigation

#42 cmawhorter opened 2 years ago
0
Suggest adding an event for `PointerInputDeviceChanges`

#41 mattrq opened 2 years ago
0
Suggest adding a `isCoarse` property?

#40 mattrq opened 2 years ago
0
Suggest adding a `firesHoverEvents` property or some way to detect that in active input device supports hover?

#39 mattrq opened 2 years ago
0
chore: fix ReSpec errors

#38 sidvishnoi closed 4 years ago
5
Is this still active?

#37 marcoscaceres opened 4 years ago
3
Add conformance section

#36 tidoust closed 4 years ago
0
[InputDeviceCapabilities] Align with Web IDL specification

#35 autokagami opened 5 years ago
1
[InputDeviceCapabilities] Align with Web IDL specification

#34 autokagami closed 5 years ago
0
Add explicit [Exposed] + default dictionary value

#33 saschanaz closed 5 years ago
3
Feedback

#32 ghost closed 5 years ago
0
Enumerate devices

#31 RByers opened 6 years ago
0
Upstream tests to web-platform-tests

#30 foolip opened 7 years ago
0
Add spaces to title: Input Device Capabilities

#29 foolip closed 7 years ago
0
Add ability to detect mouse buttons are swapped

#28 dtapuska opened 7 years ago
6
Improve reliability of mouse event from touch interaction in polyfill

#27 rafgraph opened 8 years ago
1
API to indicate a device relies on focus afforadances

#26 RByers opened 8 years ago
0
Add a supportsPointerPressure property?

#25 mustaqahmed opened 8 years ago
0
Add example for pointerMovementScrolls

#24 RByers closed 8 years ago
5
Add pointerMovementScrolls property

#23 RByers closed 8 years ago
3
Add property for whether dragging the pointer scrolls

#22 RByers opened 8 years ago
5
Make example a bit DRY-er

#21 patrickhlauke closed 8 years ago
4
Fix URLs

#20 mathiasbynens closed 8 years ago
1
If 'InputDevice' isn't about the device itself, but about its capabilities, rename the interface?

#19 smaug---- closed 9 years ago
7
Add additional keyboard event input tests

#18 RByers closed 9 years ago
1
Should we add a firesPointerEvents property?

#17 jacobrossi opened 9 years ago
2
Interaction with IME

#16 TakayoshiKochi opened 9 years ago
2
Expand introduction to better describe problem/use case

#15 patrickhlauke closed 9 years ago
2
Expand introduction to better describe problem/use case

#14 patrickhlauke closed 9 years ago
3
Touch not detected properly on Windows Phone

#13 RByers opened 9 years ago
0
Should init*Event methods clear the sourceDevice?

#12 RByers opened 9 years ago
1
Polyfill should hook document.createEvent

#11 RByers closed 9 years ago
0
CompositionEvent polyfill doesn't work in Firefox: Illegal Constructor

#10 RByers closed 9 years ago
0
Need more precise W3C language / formatting

#9 RByers opened 9 years ago
0
Should the spec define any event-specific behavior?

#8 RByers closed 9 years ago
11
Verify the tests pass with the polyfill on a few other browsers

#7 RByers closed 9 years ago
1
Add tests for pointer events

#6 RByers closed 9 years ago
1
What to do about scroll events?

#5 RByers closed 9 years ago
3
Add tests for non-input events?

#4 RByers opened 9 years ago
0
Add tests for composition events

#3 RByers closed 9 years ago
3
Primarily superficial wording changes

#2 tdresser closed 9 years ago
2
The spec should have a motivating example for firesTouchEvents

#1 RByers closed 9 years ago
0