Radio buttons in cgi script-generated html page stopped working after upgrade to Firefox 4 (from 3.6.16).
I disabled both of the Firefox Add-Ons I use (NoScript 2.1.0.1 & Ad Block Plus 1.3.6) and rebooted the machines, but that had no effect. This problem has been repeated on multiple PCs, running XP Pro (sp3), Vista Business (sp2) & Server 2003 (sp2), right after upgrading to Firefox 4, so the problem is definitely related to Firefox 4.
Chosen solution
This could be related to the new HTML5 rendering engine. To test that possibility, you can temporarily disable it.
- Open about:config
- In the filter box, type or paste html5 and pause until the list is filtered
- Double-click html5.parser.enable to toggle it to false
If it works after that, there may be some layout problem with your form (i.e., accepted in HTML4 but not accepted in HTML5), or you may have found a bug.
This forum focuses on end-user support. You can find more web development help on the mozillaZine Web Development board. Separate forum, separate registration. Please note the tips in the Sticky Post at the top of the forum before posting.
Read this answer in context 👍 0All Replies (4)
Chosen Solution
This could be related to the new HTML5 rendering engine. To test that possibility, you can temporarily disable it.
- Open about:config
- In the filter box, type or paste html5 and pause until the list is filtered
- Double-click html5.parser.enable to toggle it to false
If it works after that, there may be some layout problem with your form (i.e., accepted in HTML4 but not accepted in HTML5), or you may have found a bug.
This forum focuses on end-user support. You can find more web development help on the mozillaZine Web Development board. Separate forum, separate registration. Please note the tips in the Sticky Post at the top of the forum before posting.
That fixed it (on all the PCs)!! I suppose it could be an issue with our cgi scripts, but they've been working fine for the past dozen or so years until the upgrade to Firefox 4. I don't know if Microsoft shifted over to html5 with the recent release of IE9 (which we've been using for the past few days...since they stopped working in Firefox 4), but they work fine in IE. Thanks for the quick solution!
Modified by freddy3
If this is an internal-use-only application, it sounds as though you're done. If it's a public-facing application, it would make sense to take a deeper look at the page.
It's internal only, but the code is widely-used, so I'd reckon there'll be many similar complaints in the coming weeks. Thanks again!