Mozilla Details Firefox 3.6, Publishes Roadmap

                   

The browser wars are well underway. Apple released a beta for Safari 4, Chrome 2.0 is in beta, Internet Explorer 8 has just been released, and Firefox 3.5 is almost here. Still, that isn’t stopping the Mozilla team from looking ahead, beyond Firefox 3.5. They call it Firefox 3.6, but since that version number is likely to be bumped higher, they actually prefer the code name Namoroka, or the alternative name Firefox.next. A new roadmap for Namoroka has been published, and it details some interesting goals.

 

Namoroka will continue to improve on performance. However, the focus will be on the interface and the application itself; startup times, time to open a new tab, and user interface responsiveness. Continue reading

Advertisements

IE8 gains market share at Microsoft’s own expense

                  

New browser cuts into IE7’s market share, while Firefox, Safari and Chrome boost theirs

 

Gains made by Internet Explorer 8 (IE8) since its launch last Thursday have come at the expense of the older IE7, according to data from Irish metrics firm StatCounter.

And while IE7’s market share has fallen by 2.6 percentage points since last Wednesday, the day before Microsoft Corp. released IE8, most rival browsers showed significant gains, giving credence to the idea that Microsoft’s newest venture has not pushed users of its competitors to switch. Continue reading

Chrome beats the hackers in annual browser bash

The Pwn2Own competition, which is held every year to challenge hackers and security experts to find vulnerabilities in web browsers and mobile devices, has taken its usual share of victims with one surprise survivor during its first day.

Targeted browsers included Microsoft’s Internet Explorer 8, Mozilla’s Firefox, and Google’s Chrome, running on a Sony Vaio notebook running Windows 7 as well as Safari and Firefox on a Macbook running OS X.

Continue reading

Pwn2Own: IE8 hacked & Microsoft responds in less than 12hrs

                        

TippingPoint’s 3rd annual Pwn2Own contest has already shown significant security breaches on Apple’s Safari, Mozilla’s Firefox and Microsoft’s Internet Explorer 8, but Google’s Chrome was the only browser that made it through the first day of testing this year.

One of the contestants, Nils was able to exploit the latest Internet Explorer 8 which was released just few days back. The blogosphere and news websites picked it up and very soon it became a hot news around. When people were worried about IE8’s security, MSRC (Microsoft Security Response Center) had already reproduced and validated the IE8 vulnerability in less than 12 hours.

Microsoft is expected to release a security patch for this vulnerability very soon. It is infact surprising to see that IE team acted so fast even when they were busy at MIX09!

You can visit TippingPoint’s blog for more information.

Related Post Chrome last browser standing after day one of Pwn2Own

Chrome last browser standing after day one of Pwn2Own

       

Google’s Chrome browser is the last web browser standing after day 1 of Pwn2Own. Does this make you reassess your daily browser?

A recent contest at CanSecWest, an event that brings together some of the most skilled experts in the security community, has demonstrated that the three most popular browser are susceptible to security bugs despite the vigilance and engineering prowess of their creators. Firefox, Safari, and Internet Explorer were all exploited during the Pwn2Own competition that took place at the conference. Google’s Chrome browser, however, was the only one left standing—a victory that security researchers attribute to its innovative sandbox feature.

I have to admit that while Chrome isn’t my default browser, I’m  quite fond of it. Its ability to handle countless tabs and Windows being open (as long as you have enough RAM) is far superior to any of the other big browsers. It’s also very stable and I’ve never had a crash that’s managed to take out all the tabs or make the wheels fall off the OS. The fact that Chrome’s survived day 1 of Pwn2Own makes me think that Google could set the security benchmark in much the same way that it is currently the speed pace setter.

Sure, Chrome doesn’t have all the bells and whistles that other browser have (and no add on support like Firefox) but it’s a fast, robust, and i seems secure bit of code.

Chrome is a browser worth keeping an eye on.

by Adrian Kingsley-Hughes

Related Post 

Google offers better-tested Chrome version

Google released a new beta version of Chrome Tuesday, offering a better balance between software that’s stable but out of date on the one hand and cutting-edge but crash-prone on the other.

The new version offers a number of new features, including zooming that increases or decreases the graphics as well as text; autofill to ease the chore of re-entering information in Web site forms; and new tab-dragging features that let you dock browser windows to the sides of the screen. The new beta version is essentially the same as Chrome 2.0.169.1 that was released last week to the Chrome developer preview channel for less-tested versions of the browser, Google said.

The feature Google chose to spotlight in a blog post announcing the new Chrome beta, though, is better JavaScript performance from a new version of the browser’s V8 engine. “It’s 25 percent faster on our V8 benchmark and 35 percent faster on the Sunspider benchmark than the current stable channel version and almost twice as fast when compared to our original beta version,” Chrome product manager Brian Rakowski said in the blog post.

JavaScript is used to power elaborate Web applications such as Google Docs and refinements on countless more ordinary Web sites, and Google, Mozilla, Apple, and Opera all are racing to improve how well their browsers handle it.

Since releasing Chrome 1.0 in December, Google has essentially offered only two of the three promised versions of its browser: that stable version, which has received only minor tweaks, and the very rough-around-the-edges developer preview version where Google tries out new features. The beta version just tracked the stable version.

I’ve been using the developer preview version for the most part, despite the fact that several earlier incarnations were prone to becoming unresponsive and the latest one triggers an objection from Flickr’s Organizr tool. Recent Chrome developer preview bug fixes have helped, but it’s still not for most folks.

The better-tested beta, though, means many of the new features will be available to those with a lower tolerance for flakiness.

New how-to document for extensions
One big advantage Firefox has over Chrome is its ability to accommodate extensions that endow the browser with new features. Google is working on the extensions for Chrome, though, and on Monday Google programmer Aaron Boodman published a how-to document for writing Chrome extensions.

“Right now extensions can only really contain content scripts, so that is all this doc covers. But we’ll be expanding it over time as more features develop,” Boodman said in an e-mail announcement of the how-to document.

Download Now