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

tangentialPressure support in browsers #192

Closed
patrickhlauke opened this issue Apr 4, 2017 · 13 comments

Comments

@patrickhlauke
Copy link
Member

commented Apr 4, 2017

Wondering if there's any plans for browsers to actually implement tangentialPressure https://w3c.github.io/pointerevents/#dom-pointerevent-tangentialpressure - we've always looked at this as a nice-to-have for completeness' sake, but to my knowledge there's currently no real-world implementation of it.

If there's no desire/appetite for this to be implemented any time soon, I fear we're probably better off reverting/pulling the feature.

Thoughts?

@dfleck

This comment has been minimized.

Copy link

commented Apr 4, 2017

If anyone needs hardware for testing I might be able to help.

@mustaqahmed

This comment has been minimized.

Copy link
Contributor

commented Apr 4, 2017

Chrome is shipping tangential pressure & twist with complete low-level plumbing in Mac on M58 (expected end of this month).

We tested the implementation with Wacom tablet plus INTUOS4/CINTIQ21 DTK2100 Airbrush Pen.

@patrickhlauke

This comment has been minimized.

Copy link
Member Author

commented Apr 4, 2017

whoah there, out of left field there @mustaqahmed ... i was already thinking we'd have to axe this.

@patrickhlauke

This comment has been minimized.

Copy link
Member Author

commented Apr 4, 2017

assuming Windows will also follow at some point?

@mustaqahmed

This comment has been minimized.

Copy link
Contributor

commented Apr 4, 2017

On Chrome for Windows, "twist" should be visible soon but not sure about "tangentialPressure" since Windows WM_POINTER API doesn't seem to support the latter.

Here is the chromium bug for this work in progress by @SummerLW.

@NavidZ

This comment has been minimized.

Copy link
Member

commented Apr 27, 2017

Just to follow up on this blocking issue since we need to decide whether to keep this attribute in v2 or not.
@patrickkettner @smaug---- @mingchou Do you think this feature will be available in Edge/FF anytime soon?

@NavidZ

This comment has been minimized.

Copy link
Member

commented Jun 5, 2017

@smaug---- @mingchou I was reading the MDN for pointerevents and realized these are implemented since FF54. Can you confirm this? If you guys having this as well I guess we should be good with including this in V2. Right?

@mingchou

This comment has been minimized.

Copy link

commented Jun 7, 2017

We just added the attribute since FF54 but not yet give it a real value.

@NavidZ

This comment has been minimized.

Copy link
Member

commented Jun 8, 2017

@mingchou do you think you can manage to get it in sometime in the near future? I'm asking to see whether we would like to include this in V2 or not.
@patrickkettner do you know about Edge regarding this issue?

@mingchou

This comment has been minimized.

Copy link

commented Jun 14, 2017

I created a patch (to support tangentialPressure on Mac) but I'm waiting for a device to test it. Hopefully, land it in FF 56 or 57. Btw, we only enable PE on the nightly build and so far we don't have a concrete schedule to enable it in the release.

@NavidZ

This comment has been minimized.

Copy link
Member

commented Jun 14, 2017

I believe as long as there is a version of the browser that supports the feature and pass the tests that will be enough as it is a proof of concept that the implementation is possible and not vendor dependent. So even nightly builds would be fine. @patrickhlauke am I right?

@patrickhlauke

This comment has been minimized.

Copy link
Member Author

commented Jun 14, 2017

yes, and the requirement of 3 interoperable implementations is only really important once we want to fully move to REC (related, I know I've been super-slack with keeping on top of things here, will set some time aside to see where we're up to in that respects soon)

@NavidZ

This comment has been minimized.

Copy link
Member

commented Jul 28, 2017

I assume we can close this one as we will have the implementations ready. Feel free to open this again if you think otherwise. I'm going to follow up with other vendors and send an updated test results to the working group mailing list so we can see where all browsers stand in terms of the tests.

@NavidZ NavidZ closed this Jul 28, 2017

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