Not sure if this is due to the originally stated issue, but it may be related to those experiencing an asymmetric reaction to sending a button response between Chrome and IE.
IE, in some cases, is more forgiving than Chrome. I found this discussion, while the study is similar in appearance.
In my form, the problem was the most common, located about 18 inches from the monitor. Somehow, in my encoding, I gave a div that contained the container of the form id = 'contact', and the form had name = 'contact'. The submit button worked in IE, as expected, with this layout using form = 'contact' in the submit button. However, Chrome ignored button clicks without any hints as to why in the console.
After a short time spent on various alternatives - creating onclick events in the submit button, etc., I accidentally stumbled upon a real problem. (the form identifier seems to be the authoritative handle for Chrome, while IE seems to take on the value of the name?)
Entering this here if someone else stumbles upon this scenario.
I saw this effect again - IE also more forgives inconsistent curly braces, while Chrome didn't play - ignored the code that referenced the document.
source share