A user of my add-on reported that since I upgraded to the newest SugarJS, he can no longer type "10:" into a date field and have it parsed as 10 o'clock, even though that previously worked.
Thanks for posting this... I suppose this is a regression so I will mark it as a bug, even though I'm on the fence about whether it's an actually valid format or not....
A user of my add-on reported that since I upgraded to the newest SugarJS, he can no longer type "10:" into a date field and have it parsed as 10 o'clock, even though that previously worked.