You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The test with name "Calendar selection works on different timezones" is disabled via the following PR: #4428
Enabling strict parsing for the ui5-date-picker component formatter by default causes this particular test to fail.
There is a mocked Date.prototype.getDate method in the test sample, which alongside with strict parsing set to true causes the
DateFormatter to not be able to parse the string values from the input fields.
The DateFormat's parse method wasn't expected to call getDate on the already correctly parsed JS Date :( However the result is declared invalid and replaced with null when the day does not match the one from the string. As we do not have a way to mock the JS Date, I suggest to delete the test.
Hello colleagues,
Bug Description
The test with name "Calendar selection works on different timezones" is disabled via the following PR: #4428
Enabling strict parsing for the ui5-date-picker component formatter by default causes this particular test to fail.
There is a mocked Date.prototype.getDate method in the test sample, which alongside with strict parsing set to true causes the
DateFormatter to not be able to parse the string values from the input fields.
Steps to Reproduce
$0.getFormat().parse("Jan 1, 2019")
Expected Behavior
A JS date object should be successfully generated by the parse method. Instead the parse method
returns
null
.Isolated Example
Use the test page, which is relevant to the particular test: http://localhost:8080/test-resources/pages/DatePicker_test_page.html
Context
Best Regards,
Boyan
The text was updated successfully, but these errors were encountered: