Input readonly still can change the date, bug or not?

[itajackass]

Prerequisites

• I have searched for duplicate or closed issues.
• I have validated my setup against the latest version on StackBlitz.
• I have read the contributing guidelines.
• I understand that only sponsored issues will be worked on and that if I wish to sponsor an issue, I will contact the owner FIRST.

Describe the issue

Hi, I recently migrate from old bootstrap3 datetimepicker to latest tempus dominus v6.
After a lot of migration code, all is working but i see that input set as readonly now can be still edited with tempus dominus ( with old datetimepicker, if a field got a readonly attribute, it can't be modified).
I know i can set "disabled" instead "readonly" to solve this issue, but you know during form submit, "disabled" inputs are not submitted....
So i prefer use "readonly" when i can..... any suggest to disable tempus dominus from firing calendar when input has a readonly? Thanks

StackBlitz fork

https://stackblitz.com/edit/tempus-dominus-v6-simple-jquery-setup-mgzzdu?file=index.html

What operating system(s) are you seeing the problem on?

Windows

What browser(s) are you seeing the problem on?

Firefox

What version of are you using? You can find this information from the sample StackBlitz.

6.9.9

What your browser's locale? You can find this information from the sample StackBlitz.

it

[Eonasdan]

This is not a bug. I mentioned this in some other discussions, that I think it's odd for the picker to dictate the behavior of the fields and buttons. If you want it "disabled" you should modify the add-on button