google chrome not submitting form (js errors?)

Question

I can't get Google Chrome to submit my form. It's getting pretty ridiculous. It ends up focusing a random form field (but it's the same one every time) instead.

No issues with FF or IE...

Two of the errors Chrome gives me in developer tools are:

An invalid form control with name='state' is not focusable.
An invalid form control with name='unitName' is not focusable.

BUT, these aren't even the one field that chrome is deciding to focus on. I'm at a loss, any one had any experience like this??

are you able to show us some code? what do your forms and JS look like? — Alastair Pitts, May 24 '11 at 01:42
Well, it's an enormous form I'll be honest... but i have many similar forms to this, and they have no problems. — Shackrock, May 24 '11 at 01:44
Is there any structural difference between your working forms and this non-working form? — Alastair Pitts, May 24 '11 at 01:46
You probably have two form fields named `state` and `unitName`; can we see those? — Jimmy Sawczuk, May 24 '11 at 01:48
Want to add that the correct answer to this is: `maxlength caused issues. I removed them all, and no more woes.` I'm sure this may be a common issue for those using jQuery to aid in populating fields w/ Chrome. — Shackrock, Nov 29 '11 at 21:32

score 5 · Answer 1 · answered Sep 18 '12 at 23:57

5

I had this exact problem with an input field marked "required" that was made invisible via javascript. Chrome could not display "please fill out this field" so it said An invalid form control with name='description' is not focusable in the console.

answered Sep 18 '12 at 23:57

Stephane Rainville

446
6
15

Same here. Found similar question here: http://stackoverflow.com/questions/7168645/invalid-form-control-only-in-google-chrome – Kevin Tighe Feb 25 '13 at 13:19
Has anyone got code that can catch this error so we can handle it in Javascript? can't exactly wrap a try{} block around a form submission! – hood Jul 10 '13 at 03:44

score 4 · Accepted Answer · answered May 24 '11 at 01:50

4

Without seeing the HTML, here's what a little Google'ing turned up:

The root of the problem appears to be assigning a maxlength attribute to a form field that is automatically populated by the browser, with a value that is longer than the maxlength limit.

answered May 24 '11 at 01:50

no.good.at.coding

20,221
2
60
51

@Wesley Exactly! :) I removed it from my answer though, it seemed better suited to a comment – no.good.at.coding May 24 '11 at 01:53
maxlength it was. I removed them all, and no more woes! Thanks man!! – Shackrock May 24 '11 at 02:04
1

thanks - for me it was a required field, hidden via the tagInput plugin – Peter Ehrlich Feb 22 '13 at 09:06

score 1 · Answer 3 · answered Jul 09 '13 at 19:55

1

I just had a similar problem, and for me, the fix was adding type="button" into my <button> tag.

answered Jul 09 '13 at 19:55

caleb

2,687
30
25

google chrome not submitting form (js errors?)

3 Answers3