This nearly caused me to have a heart attack ! I advise all of my clients to use firefox as it is the best browser I know of in my opinion, however with a new client they download firefox 4 and when they went to use my photo upload area it was not working, I have 3.6.16 and all works fine so I logged into their computer to check and tried nearly every admin system i have designed and none of the photo upload areas worked when the form was submitted it simply refreshed the page not putting any info in the database or moving the image to the upload folder, I was convinced I had a system wide bug with the script I designed and spent hours trying to figure it out, only to find out today that if they downgrade to 3.6.16 everything works just fine ! This is the first time I have ever known any problem with Firefox and think this should be addressed immediately ! Thanks guys.

If you go to http://gizmodo.com/#!classic?p=1 and scroll to the bottom and press the "previous" button - nothing happens. This is reproducible every time for me. Can anyone else click that button with results?

I tried the link mentioned by sungkhum and it is working fine with me. i had a similar issue with a web application I am working on. After couple of days of debugging i discovered the reason.

FX4 implements the HTML5 standards. and with HTML5 if you have the attribute [required] on any HTML element inside a form, it means that this field is required and the form cannot submit until the field is filled in. sometimes the attribute would be added to a hidden element so the message that indicates that the field is required would not be visible as well.

also to be noticed that with HTML5 having [required="false"] would not make any sense, since the way HTML5 sees it is, if you write in the Boolean attributes that means they are true even though you have the ="false". to have the attribute as "false" you do not mention it.

so the short of it is, make sure that the page you are facing this issue with does not have any [required] attribute mentioned in it. check the "view page source" and search in there.

Good Luck

Actually to reproduce the problem with Gizmodo you must go directly to http://gizmodo.com and make sure you are in classic mode then type http://gizmodo.com in the location bar and hit enter. Then once the page is loaded click "Next" at the bottom of the page. Once the page reloads, try hitting "Previous" or "Next" On my system neither button works and there is no "required" element in their form as tameem_e suggested to look for.

Check if you have a form inside the form you try to submit !

I had the same issue and noticed that firefox behavior changed from version 3.6 and 4:

- In firefox 3.6 (or google chrome)the browser will not complain if there is a form inside another form

- in 4 the submit button for the "parent" form will end up outside the form and submit will therefore not work

note that form inside form are against W3C standards...

No, it doesn't look like there is a form within a form - but that is interesting information that possibly could have affected some pages in the past that I have visited. But still gizmodo's next and previous buttons can't be pushed and there are no forms within forms.

I noticed that the problem seems to only affect html using the <button type="submit" /> element and not the <input type="submit" /> element.

I've noticed that there is also a problem when trying to view the activity logs in WLFS when you're using FF4... I have to use Chrome or IE9 in order to view this, and it's frustrating having to switch back and forth between browsers...

I have the same issue. I tried to submit a form to receive a sample from Walmart, and it never works. The latest example was at the webpage: https://secure.startsampling.com/sm/walmart/captureAddress.iphtml?item=101650&source=&url=http://www.startsampling.com/sm/goldbond101650&key=2c85c6ea82f739a322599be784dc15b5

You know, it seems a bit ungrateful when you complain about free stuff but sometimes free stuff can drive you up a wall, for instance FF 4.0. Not only does programmers get a kick out of redesigning things even though there's no need to do so but they tend to add things that just doesn't cut the mustard. I specifically waited for FF 4.0 thinking that most of the bugs would be ironed out of simple procedures like click buttons (i.e. post reply, enter, continue etc.) but FF 4.0 has made me want to pull out my hair by the hand fulls! I needed to update my payment information in my Juno account to no avail, the site accepts the click of every button on the site except.... You guessed it, the submit button after I've entered my new information. This has been going on with the prior 2 versions of FF and now has continued into FF 4.0. The tech team at Juno has informed me that there is nothing wrong with their site it's obviously a software problem but not their software and now I'm starting to believe them.

This has caused problems with my bank and other sites since this has been happening. I believe that it's a java or javascript thing because I've had problems with that since the previous 5 versions of FF, it just never seem to have been fixed sufficiently. Sometimes it work sometimes it don't. Now I haven't been able to update my payment information on Juno and believe it or not I was told that is the only way that I can pay Juno is through their site because they don't have a USPS address that I can mail it to. Nor can I update the payment from paying by credit card to paying by check... Go figure! Good thing that most people don't have just one email account or I would be screwed at this point. I've had to juggle my contact emails in order to receive mail form my bank and other important contacts. Is it me or all of the web browsers experiencing bug problems in their software due to them trying to out do each other?

My library has a form to submit your card # to access online data. When I upgraded to 4.0 the form stopped working. The Library insisted the form worked because they tested it with IE and FF3.xxx. I dug into it and found that the form was laid out in multiple table data cells, NOT allowed in html. IE and FF 3.xx ignored that faux pas and kept working. FF 4.x refuses. I re-wrote the page to eliminate the multiple cells and it works like a champ. I just have to get the library to fix their code. The upshot is that FF 4.0 is much more strict about non-compliant code and will continue to cause problems until web designers get compliant. (or FF4.xx gets "looser")

In my particular case it is a php form that submits back to it's self. In other words a form on index.php with the action attribute set to "index.php" so if certain data is submitted the form will not show but if not, the form will show. I can see when I click the submit button that it doesn't even attempt to reload the page. This is common usage in simple php web apps with forms so for now the only resolution is to go back to using IE :-( Can't go around changing all the web apps in the world that use this just so I can keep using FF (thought that's something that would normally be expected from M$). I'm sure it's just a bug that will get fixed eventually.

I'm having this problem at www.vvmo.com on the search page if you search for something , say "Velvet Underground cd move back" , you then cannot add this CD to the cart and checkout. Only with version 4.

Just tried the Firefox 5 beta and this is still an issue.

I found a good solution! I had this issue with submit just after updating to Firefox 4. My workaround was simple (in my opinion)…it also works across the browsers. I just made the submit button into just that…a button. Create a button instead of the typical input type=submit. for example: <button type="submit" value="submit" class="button"><img src="your image" /></button>
Notice the class. I didn’t like the automatic styling that the browsers give to buttons so I stripped the background, margin, padding, and border in a simple style sheet. Now it works just great! Hope this helps someone!

Hello. Well this is disturbing news. We have some 300 web pages rendered with XSL. All worked fine pre-FF4. With FF4 what we seem to be seeing is that fields with the required attribute set to "true" are required as expected, and fields with required="false" are not required as expected, but fields with the required attribute not set at all are defaulting to required now. Previous to FF4 they defaulted to not required. That is the vast majority of our fields! So I take it there is no way to change this at the Firefox level?