Add autoOpenDisabled property

[niiyeboah]

When datePicker.autoOpenDisabled = true:

• Focusing and typing in field doesn’t open the overlay
• Clicking on icon opens the overlay
• Up / Down keys opens the overlay

[web-padawan]

@jouni do you have an idea how this should behave, keeping #434 in mind?

[web-padawan]

Note, potential workaround would be to check for _noInput.

[tomivirkki]

The feature design document we agreed upon states that "Mobile UX should stay as it is"

[tomivirkki]

Ping @niiyeboah, the build is red

[niiyeboah]

If you type the value to the field and blur, it's always marked as invalid:

This should be fixed now

[tomivirkki]

esc and enter buttons behave strangely with the new feature:

If you haven't yet opened the dropdown and type a value without opening the dropdown:

• ESC does nothing (should revert the changes to the input as previously)
• Enter does nothing (should apply the input's value as previously)

If you have opened and closed the dropdown earlier and type a value without opening the dropdown:

• ESC applies the input's value as the date picker's value (should revert the changes to the input as previously)
• Enter seems to work as expected

[tomivirkki]

If you input a value to a date picker and focus another one, you enter some kind of an eternal loop on IE11:

Please test the feature on all supported browsers

[niiyeboah]

Rebased and refactored the implementation. Apologies for not testing all browsers 😞

[web-padawan]

@yuriy-fix let me request your review as you have recently changed validation logic.

[tomivirkki]

If I select a value and press esc, the input value is set as the ISO value of the component....and then blurring the field will make it invalid

[web-padawan]

@yuriy-fix @tomivirkki updated validation logic and added tests. PTAL when you have time.