Rick Byers

Let's leave this issue open until there's been some more discussion and the tests and polyfill have been updated (not something I expect to do before I get back from...

Makes sense to me (pretty similar to the "touchpad direction reversed" capability we've discussed previously). But can you describe the use case? > The only problem I see with using...

Thanks, those use cases seem really compelling to me! So are you thinking something like this? ```webidl partial interface InputDeviceCapabilities { // When true, the device represents a mouse where...

> If the information is used in UI, one should be able to query it without any user input... but then, that would be a privacy issue... IMHO if we...

Are you suggesting that you'd get a different InputDevice object depending on context (event target, etc.)? Or do the properties on a given device change with context (i.e. the keyboard...

@TakayoshiKochi thank you! My motivation at the moment is just around pointing devices (as you can see by the only defined property being `firesTouchEvents`), but the goal is definitely to...

Here's some references for the context I gave in the meeting for why I argued this was potentially extremely important for payments ecosystem: - With tracking (including fingerprinting) being clamped...

Part of the challenge here is that there's so many different use cases, multiple layers of abstraction which may each weigh in on trust decisions, and so many possible different...

> I don't understand the proposal to be that the determination would be made on anyone's whim. Data protection authorities, for example, seem entirely unwhimsical to me. Oh yeah, if...

We had a great long discussion on the call today which @timcappalli is going to summarize and share notes for. My main takeaway personally was that the protocol registry we're...