You’ll probably have a hard time believing this. But Microsoft actually just asked developers to “please adhere to web coding standards”. Now while I agree with following the standards, it just comes across as a joke when it’s from them.
I must say, this is a prime example of why you should never stop learning as a developer. It seems a few of us more experienced developers didn’t know this. Some of the solutions seem bizarre too like hiding the button, using JS to detect the enter key and so on.
It does seem a bit backwards that if you have multiple forms, you’ll need some kind of hidden input to set an ID for that form but hey, this is MS.
A little further testing though, and I see that if you have only 1 input, then the enter key does not work but if you have more than 1 input, the enter key does work. I can’t think of any forms that I have created that have only 1 input field though.
MS screwing the web with IE since 1995.
Like I said, echo str_rot13(“Shpx Zvpebfbsg!”);
[member=72272]astonecipher[/member], in my last example if your form was multiple unchecked check boxes it will still fail always. There are a few common instances where a form would be all check boxes such as selecting multiple rows in a table for some bulk action.
A little further testing though, and I see that if you have only 1 input, then the enter key does not work but if you have more than 1 input, the enter key does work. I can't think of any forms that I have created that have only 1 input field though.Yet another quirk. Tested and verified (IE8). Thanks Mr. Gates,
This is not a Microsoft problem. It’s a problem of reyling on weird side effects instead of explicitly checking the request method and data.
In a sense, Microsoft is actually doing the right thing: They don’t give a damn about submit buttons. If your entire application depends on some submit button, I’d say this is the real problem.