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

Add property for whether dragging the pointer scrolls #22

Open
RByers opened this issue Jul 28, 2016 · 5 comments
Open

Add property for whether dragging the pointer scrolls #22

RByers opened this issue Jul 28, 2016 · 5 comments
Assignees

Comments

@RByers
Copy link
Member

RByers commented Jul 28, 2016

In the Pointer Events hackathon it was discussed that there's no good way to know if a user would expect a pointermove event to trigger scrolling. Eg. for a library trying to implement a custom scroller that behaves like the native OS scrollers (eg. iScroll). A naive thing to do is to trigger scrolling for pointerType="touch" only, but that won't handle the case of touch-like stylus devices (eg. Samsung SPen).

We should just add a new property to InputDeviceCapabilities that indicates whether this is a pointer where movement typically causes scrolling. For chromium this will probably always have the same value as firesTouchEvents.

/cc @scottgonzalez @jacobrossi @mustaqahmed @dtapuska @tdresser

@RByers RByers self-assigned this Jul 28, 2016
@RByers
Copy link
Member Author

RByers commented Jul 28, 2016

Probably the main question here is what the property name should be. Ideas:

  • draggingScrolls
  • pointerMovementScrolls
  • scrollByDragging

@tdresser
Copy link
Collaborator

Should the name be specific to scroll? Or should it also refer to whether pointers can cause zoom?

@RByers
Copy link
Member Author

RByers commented Jul 29, 2016

I think it should be scroll-specific. Eg. I think the SPen can scroll but not zoom (and if not, certainly it would be reasonable for some pens to act that way).

@RByers
Copy link
Member Author

RByers commented Aug 2, 2016

Note that it's tempting to describe this as "is direct manipulation" - i.e. is the input metaphor one where the user is directly grabbing things on the screen. I think I'll put some text like that in the prose, but IMHO it's probably best to keep the property name very concrete around a specific capability.

@RByers
Copy link
Member Author

RByers commented Aug 2, 2016

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 vacation late Aug).

@RByers RByers reopened this Aug 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants