TimeTextBox: lenient parsing of times not working

[Adam Peller]

see dijit/tests/form/test_TimeTextBox.html, tested on FF3/Mac

1. In the second box, change 5:45 p.m. to 5:45 pm or 5:45pm. An error indicator will not be shown, but the drop down choices disappear, and if you hover over the arrows you get exceptions like

this.timeMenu.childNodes[0] is undefined
[Break on this error] var index = this.timeMenu.childNodes[0].index;
../../.....Picker.js (line 339)
Index or size is negative or greater than the allowed amount" code: "1
[Break on this error] var index = this.timeMenu.childNodes[0].index;

2. Enter a value using "AM" or "PM" in uppercase, and you get a warning icon (and still no drop down) even though the value is parsed and accepted when you change focus.

dojo.date.locale.parse should accept all of these forms, unless strict:true is set.

[Douglas Hays]

dojo.date.locale.parse("5:45:00 P.M.", {formatLength:"medium",locale:"",selector:"time",fullYear:true}) returns null

[Adam Peller]

I think the translation scripts were erroneously picking up an alternate translation with the periods for "a.m." and "p.m." in Dojo 1.2. The current dojo.cldr definition uses "AM" and "PM" for English. The non-strict parsing should permit "AM" and "PM" where A.M. and P.M. are the given localizations, but the reverse is not true -- it's not really possible to know which localizations permit extra periods.

Running with the latest code, none of this is a problem anyway, even if I put the periods back in dojo/cldr/nls/en/gregorian.js for AM and PM, everything parses properly.