This is a hotfix where we make sure to remove the type="date" attribute no matter what, and re-add it back when we want to use the native date picker.
This is to ensure that the default browser behavior does not kick in for the inputs default date behavior, where the inputmask library is used instead.
Does this PR introduce a breaking change?
[ ] Yes
[x] No
Checklist:
The following tasks should be carried out in sequence in order to follow the process of contributing correctly.
Reminders
[x] Make sure you have implemented tests following the guidelines in: "The good: Test".
[x] Make sure you have updated the cookbook with examples and showcases (for bug fixes, enhancements & new components).
Review
[x] Determine if your changes are a fix, feature or breaking-change, and add the matching label to your PR. If it is tooling, dependency updates or similar, add ignore-for-release.
Which issue does this PR close?
This PR closes #3337
What is the new behavior?
This is a hotfix where we make sure to remove the type="date" attribute no matter what, and re-add it back when we want to use the native date picker.
This is to ensure that the default browser behavior does not kick in for the inputs default date behavior, where the inputmask library is used instead.
Does this PR introduce a breaking change?
Checklist:
The following tasks should be carried out in sequence in order to follow the process of contributing correctly.
Reminders
Review
When the pull request has been approved it will be merged to
developby Team Kirby.