Respecting readOnly prop

Howdy,

SingleDatePicker.jsx I am able to pass in the readOnly prop but it only works if the prop itself is true. If I specify false, it’s not respected on touch devices because of the isTouch logic here.

There are two ways of solving this:

• react-dates stops enforcing behavior on touch devices (ripping out the isTouch logic in the DateInput component)
• we remove the default value of isTouch to be false in the DateInput component.

Let me know which you prefer and I’ll make a pr. Thank you!

[aschiopu]

In other words, I don’t think either of your suggestions is a good way to solve this.

@ljharb You haven’t mentioned why DateInputdictates the behavior of the component on different devices? It’s something that the consuming parent component can dictate easily making this component more flexible and re-usable.

@majapw I understand the reasoning behind having it read only for most touch devices, except the Surface and most windows laptops. More and more windows laptops come out with touch screens, yet they still have a keyboard and mouse.

Overall I think think this behavior/logic should probably be dictated by the parent consuming component as it relies on the devices that use of this component. The windows machines might not be the case at AirBnB, but it could be true at other companies.

[majapw]

Will be in the next release! ✌️