Having just spent 2 hours swearing violently at my computer, I thought I'd share this little bug tracking story...
I am writing a simple data entry page that contains a couple of date fields, for which I'm using the very nice JQuery UI datepickers.
I have used them all over the place with no problems at all, however on this page I was getting some weird behaviour when the submit button was clicked:
- If the date fields were empty, the form submitted fine.
- But if a date had been selected, when you clicked submit, the date picker for the first populated date field popped up and the form did not submit.
Some testing revealed this only happened in Chrome - my version of which is the v6 beta release.
An update to the JQuery UI did not fix the problem.
Some debugging code revealed that on submit, the datepicker fields were being focussed - so as far as the datepicker code was concerned, it was working correctly.
However, the object inspector in Chrome showed no unwanted event listeners that could be doing this.
Some more swearing, a minimal test case and a comparison with a working page later revealed the problem - the MAXLENGTH attribute
had been set, in a copy/paste debacle, to 8 - clearly too short for a dd/mm/yyyy date.
So, presumably, Chrome allows you to set content longer than the MAXLENGTH from script, but then will not let you submit the form, instead
focussing the offending field - it makes perfect sense when you think about it, really.
Firefox and IE both allow you to submit the form with the longer data - although you can make an argument for that making sense too. I don't know what the W3C say on this issue.
No comments:
Post a Comment