Alterna-browsers Firefox, Chrome get quick fixes
Mozilla Firefox 3.5.5 is out, just eight days after the browser updated to version 3.5.4. For Windows, Mac, and Linux, the new version of the browser fixes three bugs: one critical bug across all platforms, and then one lower priority one for Windows and one lower priority one for Mac.
The critical bug addresses crashes in the GIF decoder that was not present in version 3.5.3, while the Windows bug fixes a security runtime issue and the Mac bug fixes an HTML parser error. Mozilla Evangelist Christopher Blizzard tweeted that although the critical bug wasn't security related, it was annoying to many users. The full changelog can be read here.
The stable build of Google Chrome has been updated from version 3.0.195.27 to version 3.0.195.32. This update introduces five stability improvements, including problems with how the browser managed content from Adobe Acrobat Reader, returning to Google Maps data via the Back button, and three others.
One of the security fixes addressed not warning users of some file types that could run JavaScript, such as SVG, XML, and MHT. The other one plugged a hole that could allow for memory corruption and subsequent malicious code execution through Google Gears. The full changelog can be read here.
The developer's build of Google Chrome for Mac was also updated earlier Thursday, introducing several user interface improvements. The Copy Image feature is now fixed, auto-updates are more transparent, and multiple keyboard problems have been fixed. The full changelog for this update is available here.
Seth peers into the deep, dark corners of software so that you don't have to. He has yet to suffer a single nightmare about OS/2. You can follow him on Twitter. 
while opera runs faster then firefox without any security holes in there new update and not gathering any and all information they can get from you why would any one want to use these browsers when majority of all there features originated from opera just download opera
The Mozilla way:
1. get bug report
2. investagate
3. fix and text
4. roll out patch
Time elapsed < 3 days.
The Microsoft way:
1. Get bug report
2. Ignore or deflect blame
3. Wait for an exploit to appear
4. Wait for exploit to spread and deny responsiblily
5. Start working on a fix if the coin flip came up heads, otherwise ignore.
6. Spend 1-6 months on it even if it is a 1 line fix (if they coded properly it wouldn't break anything as long as the function contract was maintained)
7. Push out patch and claim how great they are
Time elapsed: 3 months to forever.
nowadays perfection is being able to fix your code ASAP and that why i use Firefox .
http://shaunew.gogvo.com/trial/9/
nowadays perfection is being able to fix your code ASAP and that why i use Firefox."
I agree with this! i like Firefox for its security but one needs the use of Add-ons to make full use of it, so I use Chrome as well =)
A lot of times it isn't the actual developers that are at fault. Third party vendors like Adobe do not keep up on security that are to blame. Also web developers that develop poorly designed site.
Web browsers only render what is given to them. Some do it better than others
- by softpediafan November 8, 2009 9:33 PM PST
- until Linkextend doesn't make a Google chrome extension Firefox will be my default browser (doesn't hurt to thank me for helping you discover Linkextend (for Firefox,of course)).
- Like this Reply to this comment
-
(20 Comments)