Feature Request: centralize detection of window features

[alvarosabu]

Is your feature request related to a problem?
I'm implementing a long Form with a carousel slides separate groups of inputs. I have an issue disabling the mouseDrag prop whenever the user focus on an imput and allowing it again onBlur.

It seems that this prop only configure the eventListeners on init, but doesn't change whenever the input does.

Describe the solution you'd like
MouseDrag & TouchDrag to be able to change on the go.

If any, describe the alternatives you've considered
I thought about disabling pointer-events: none; with css but then everything inside the form is useless.

Teachability, Documentation, Adoption, Migration Strategy
Well, developers will be able to change the prop according to events other thant the initialization of the component.

[quinnlangille]

Hey @alvarosaburido, I was also thinking about this recently. We're currently working on refactoring the carousel and this could be a reasonable feature. Mouse and touch drag both depend on different available features in the window.

As you've mentioned, we only check these properties on init. I'd have to think about implementation, maybe we could wrap all of our checks in one method and save results to state. This would allow us to update on the go if need be. Is that along the lines of what you were thinking?

[alvarosabu]

Hey, man @quinnlangille yeah, exactly what I meant. The next week I'm on vacation maybe I can give it a try in an MR meanwhile. If you are working on refactoring, let me know if I can contribute with it.

[quinnlangille]

Hey @alvarosaburido totally didn't see your last notification - we're still planning the refactor internally, so it likely won't kick off for a while. However, if you find yourself implementing the feature we can just port over the logic if the refactor happens after.

In the meantime, I'll rename and properly tag this. Thanks for the feature request!