Update of the update:
The 184.108.40.206 release fixed some 200 issues, but accidentally regressed a few things. Most users wonâ€™t see any difference or experience any problems, and those 200 fixes make the 220.127.116.11 update very valuable, but you should never have to choose functionality over security. So weâ€™re working fast to understand and fix these problems, and will shortly be issuing a 18.104.22.168 update to address them. The specific problems are:
- Bug 400406 – Firefox will ignore the â€œclearâ€ CSS property when used beneath a box that is using the â€œfloatâ€ property. There is a temporary workaround JS/CSS code available for web developers with affected layouts.
- Bug 400467 – Windows Vista users will get â€œJava not foundâ€ or â€œJava not workingâ€ errors when trying to load Java applets after updating. To fix this, users can right-click the Firefox icon and â€œRun as administratorâ€, then browse to a page with a Java applet â€” doing this once will fix the problem and permanently restore Java functionality.
- Bug 396695 – Add-ons are disabled after updating. Users can fix this problem by opening their profile folder and removing three files (extensions.rdf, extensions.ini and extensions.cache)
- Bug 400421 – Removing a single area element from an image map will cause the entire map to disappear. There is no workaround available at this time.
- Bug 400735 – Some Windows users may experience crashes at startup. There is no workaround available at this time.