Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spec implies mice can't support pressure #30

Closed
RByers opened this issue Jan 21, 2016 · 10 comments

Comments

Projects
None yet
3 participants
@RByers
Copy link
Contributor

commented Jan 21, 2016

The spec says:

For hardware that does not support pressure, including but not limited to mouse, the value must be 0.5 when in the active buttons state and 0 otherwise.

Which implies it's impossible for a mouse to support pressure. Force-touch touchpads on Mac OS are a real-world example that violates this, and I think we should plumb force out to PointerEvent.pressure on Mac OS.

Can we just remove the "including but not limited to mouse"? Or replace it with "(for example, most mice)"?

@patrickhlauke

This comment has been minimized.

Copy link
Member

commented Jan 21, 2016

proposing "(such as most traditional mouse and trackpad inputs)"

using "inputs" here because i find "mice", though of course correct plural form, somehow weird when talking about the computer hardware (and possibly not immediately understandable to non-native english speakers)

@scottgonzalez

This comment has been minimized.

Copy link
Member

commented Jan 21, 2016

I'm not sure that the reference is needed at all, so I'm in favor of just removing it.

@RByers

This comment has been minimized.

Copy link
Contributor Author

commented Jan 21, 2016

Thanks Patrick. Either option is fine with me.

@RByers

This comment has been minimized.

Copy link
Contributor Author

commented Jan 22, 2016

Let's land Patrick's PR for now as a step in the right direction, but keep this issue open until there is consensus...

@RByers RByers closed this in #31 Jan 22, 2016

@RByers RByers reopened this Jan 22, 2016

@patrickhlauke

This comment has been minimized.

Copy link
Member

commented Jan 23, 2016

i can see @scottgonzalez' point that it's perhaps redundant to even list examples of hardware that doesn't support pressure as it's implicit. then again, it kind of makes this more immediately clear to me (and now part of me also want to crowbar in traditional touchscreens ;) )

@scottgonzalez

This comment has been minimized.

Copy link
Member

commented Jan 23, 2016

My main concern with this wording is that over time this statement may become meaningless to new developers. We already have legacy references in HTML with <input type="radio"> which has absolutely no implicit meaning to a large portion of developers. Input devices are changing fairly rapidly and the "traditional mouse" could easily become a relic while still being referenced in this spec.

@patrickhlauke

This comment has been minimized.

Copy link
Member

commented Mar 5, 2016

Personally, I think the danger of obsolescence here (particularly as the term isn't used for an attribute name or value) is fairly low. For how do we feel then about the change made in #31 versus removing the parenthetical bit altogether? I have no major strong feelings either way.

@scottgonzalez

This comment has been minimized.

Copy link
Member

commented Mar 8, 2016

I'd still prefer just removing the parenthetical, but I don't have very strong feelings either.

@RByers

This comment has been minimized.

Copy link
Contributor Author

commented Mar 8, 2016

Either way is fine with me.

@patrickhlauke

This comment has been minimized.

Copy link
Member

commented Mar 8, 2016

At two "whatever" and one "remove" (and nobody else appearing to have any opinion on it either way either), I'll make a PR to remove it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.