regression: on blur date is not formatted
See original GitHub issueSeems to be a regression from the bug fix to Avoid reformatting user input as they type from 0.44 to 0.46. On blur, date is no longer formatted.
An easy way to test it is to set the date to 4.23.17
and then press tab
on the first example.
In version 0.44 the date is formatted correctly (changes to 4/23/17
), in version 0.46 it stays as 4.23.17
.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Html input type date losing value on onfocusout - Stack Overflow
I assume thats why the value is lost. The input value= must be in yyyy-mm-dd format. The displayed format (when type='date') is determined...
Read more >Lightning:input type="date": how to change the date fomat
NOTE:Also I have used the new <lightning:inputField fieldName="date__c" /> for dates and actually works really nice but date format is a must I ......
Read more >Format date in regression - Statalist
When I look at my data, the date will be correctly displayed as 2016Q3. However, when using this variable in a regression using...
Read more >Date Picker - Components - Paste: The Design System for ...
To change the format of the return date value, we recommend using the formatReturnDate() function on the Date Picker's onChange() or onBlur() handler....
Read more >Editor Inline Datepicker Blur Focus Issue — DataTables forums
Using moment.js for custom time formatting. ... Problem: I hit {enter} on a cell containing a date to bring up the datepicker.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @aij, thanks for the reply.
I agree that we don’t want to format on the invalid date case. When the date is valid though, as in:
I think it makes sense to format it to follow the mask defined.
If this is intentional and
4.23.1778
is not valid forreact-datepicker
when the mask isMM/DD/YYYY
, it may be worth documenting the differences between whatmoment.js
andreact-datepicker
consider valid. In my opinion, the expected behavior would be to keep them consistentThis issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.