Webware

Mozilla, racing to release Firefox 3.6 by the end of the year, issued a fifth, and likely final, beta version of the new browser.

The open-source browser backer announced the new Firefox beta (download for Windows and Mac OS X) in a blog announcement Thursday.

Firefox 3.6 builds in a feature called Personas for customizing the browser's appearance, adds the File interface for better file management such as selecting what to upload, and, my personal favorite, placement of new tabs next to the ones that spawned them.

A total of 127 bugs were fixed since the fourth beta, but this time Mozilla didn't announce any new features. The first Firefox 3.6 beta arrived in October.

Mozilla had considered issuing its first Firefox 3.6 release candidate this week: "If we can go to build today or tomorrow, QA [quality assurance] will scrap Beta 5 and we'll release RC to the beta audience ASAP," the Mozilla meeting notes said.

Google Browser Size shows how much of a Web page browsers can show on average.

(Credit: Screenshot by Stephen Shankland/CNET)

Google published a tool Wednesday called Browser Size that lets Web developers gauge how much of their pages are visible in people's browsers.

With its own analysis, the search giant found that a lot of people couldn't see the download button for Google Earth because they had to scroll before it would show in their browser. Revamping the page increased download rates 10 percent, according to a blog post by Browser Size team member Arthur Blume.

The tool loads a Web page behind a pastel overlay that indicates what fraction of people can see a particular point on the Web page. The upper left is of course 100 percent, but when the point is farther down or toward the right, fewer and fewer can see it. The overlay statistics are based on a fraction of the people who visit the Google.com home page, said programmer Bruno Bowden.

"For example, if an important button is in the 80 percent region it means that 20 percent of users have to scroll in order to see it," Bowden said.

I'm intrigued by this sort of data. It's interesting to see the jump between old-style screens with a 4:3 aspect ratio and newer HD-style models that usually are in a wider 16:10 proportion. I'd be particularly curious to see how the overlay changes from one Web page to another--for example, I'd imagine gaming site visitors have bigger screens than mainstream Web pages.

Here's a hint if you're reading this on a laptop with a modest screen size: to see more of the Brower Size overlay, try pressing Ctrl-minus to zoom out.

I spend a lot of time looking at Web pages and have no particular fondness for scrolling. I therefore appreciate various efforts to maximize browser real estate devoted to actual Web content. Perhaps Google's tool will help on the Web design end, too, helping justify redesigns to put the good stuff in plain sight.

Google's browser has passed Safari in terms of worldwide browser usage--at least by one measurement.

NetApplications' measurements of browser usage share, which track which browsers individuals use based on visits to the company's network of Web sites, gave Chrome the third-place spot after No. 1 Internet Explorer and No. 2 Firefox for the week of December 6 through 12, according to a Computerworld story Tuesday. Chrome had 4.4 percent share to Safari's 4.37 percent.

Google released beta versions of Chrome for Mac OS X and Linux on December 8. Earlier, only developer channel versions had been available. Google plans to release the "stable" versions January 12, according to the Chromium development calendar.

Take these usage share numbers with a grain of salt. Even though 0.03 percentage points still is a lot of people in the real world, it is a small fraction, and a change in Net Applications' assumptions in August led to share changes two orders of magnitude more dramatic. Weekly statistics also vary: Although Firefox cleared 25 percent share in one week of November, it averaged only 24.72 percent for the overall month.

I've asked various browser makers about how trustworthy they view NetApplications' statistics to be. The answers generally are favorable but not ringing endorsements.

Regardless of the precise details, though, the Chrome trajectory is upward: its November usage share was 3.93 percent to Safari's 4.36 percent.

And although Google relied on word of mouth for promoting its original online search product, it's taking a more active role with Chrome. The latest example: a "Chrome for Christmas" site that lets people send invitations to download Chrome.

Firefox proved that a browser not bundled with an operating system can be successful, and Chrome could show the idea isn't a fluke if its growth continues.

Google is promoting its browser through this 'Chrome for Christmas' e-mail campaign.

(Credit: Screenshot by Stephen Shankland/CNET)

3D graphics became ordinary first in games, then in operating systems, and on Thursday, it took a significant step toward being built into Web browsers as well.

The Khronos Group, which oversees the OpenGL graphics interface, announced that its work with Mozilla to bring hardware-accelerated 3D graphics to the Web has reached draft standard form. The standard, called WebGL, lets programmers who use the Web's JavaScript language take advantage of the fact that video cards can handle 3D graphics with aplomb.

The group now wants commentary from Web developers and others who might be involved with WebGL so it can be finalized. "I anticipate us moving toward a spec that is not provisional, not merely a draft, in early 2010, the first quarter," said Arun Ranganathan, chairman of the WebGL working group and standards evangelist at Mozilla.

Internet Explorer remains the dominant browser in terms of usage, but all four of its main challengers--Mozilla's Firefox, Apple's Safari, Google's Chrome, and Opera Software's Opera--are working hard, sometimes in an informal alliance, to get ahead by advancing the Web state of the art.

WebGL fits into that effort, and not just academically. All four of those browser makers have endorsed WebGL, and developer test versions of Firefox, Safari, and Chrome have it built in. Microsoft declined to comment for this story beyond reiterating its general support for standards.

Ultimately, building 3D support into the Web could advance user interfaces of Web applications--including games, the popularity of which can be a powerful incentive for upgrading to the latest technology.

It's not clear exactly how it will play out, though, Ranganathan said. The arrival of Canvas, an advanced 2D interface for browsers, has led to a blossoming of graphics work, and he expects a similar change with 3D graphics.

But don't hold your breath for Web-based first-person shooters that rival native applications. First, even if 3D is accelerated, there are plenty of other processing and user interface constraints on Web applications. Second, even after WebGL is standardized, it must be built into browsers, people must upgrade to those new versions, and programmers must learn how to support the technology.

WebGL isn't the only 3D Web work under way. Google has its own O3D project, which currently is a browser plug-in but that the company also is building directly into Chrome.

O3D is a higher-level interface, though, not a direct competitor. Details are technical, but O3D uses a retained mode approach to WebGL's immediate mode interfaces.

And of course, a decade ago there was VRML--virtual reality modeling language, a file format rather than interface. A VRML successor called X3D, though, can actually make use of WebGL, and indeed a project called X3dom aims to do just that.

(Credit: Skyfire)

The Skyfire mobile browser has gone through some dramatic design changes in the last year. The most recent version released on Wednesday continues to adjust Skyfire's visual composition--as well as its guts and performance--on Windows Mobile touch-screen and standard phones.

The changes to the navigation menu was the first thing we noticed when we booted up Skyfire 1.5 on an HTC Touch Diamond 2. Skyfire has replaced the Menu key and back button navigation with gray, balloon-like buttons that strike us as a hybrid of Opera Mobile browser and Internet Explorer Mobile. The back arrow, Home screen button, zoom control, favorites tab, and Options icons are more finger-friendly for sure, and take a cue in both looks and content from Skyfire's two strongest rivals. We also spotted two unfamiliar tabs at the top to show your recent searches and popular queries overall.

Also like Opera Mobile browser, Skyfire 1.5 gets a welcome Full Screen mode--for touch-screen users only--that you can access from the Options icon on the navigation bar. Tap it to enter full-screen mode, which hides the nav bar so you can see more screen. Tapping the screen again shows the single Options icon, from which you can exit full-screen mode.

Skyfire has not been idle behind the scenes, either. Version 1.5 has updated to Flash 10 and Silverlight 1.5, the latest stable versions of Adobe and Microsoft software for delivering rich media, like videos. Skyfire also introduces full native support for VGA and wVGA resolutions on Windows phones, smooth scrolling, and new behavior for the text field that keeps it visible on touch-screen phones when the virtual keyboard is engaged. Skyfire also boasts faster speeds, thanks to improvements to its server.

You can download Skyfire for free by pointing the mobile browser to get.skyfire.com, or can download Skyfire for touch-screen and non-touch phones via your desktop.

Just as Microsoft advanced the state of the art for programming on Windows, Google is trying to do the same with Web-based software. Its latest move: the release of Google Web Toolkit 2.0.

GWT translates software written in the Java programming language into the JavaScript code that browsers can run natively. The technology is designed to produce fast-executing JavaScript and ease the pains of incompatibilities among different browsers.

Google Web Toolkit, released Tuesday night at a Google Campfire One developer event, fits in with the company's general push to make the Web a more powerful foundation for applications, not just static Web sites. The financial reasoning the company offers boils down to this: more use of the Web means more searching on Google and more search advertising revenue.

GWT is an open-source tool. Among the newer Web sites Google built with it are Wave, Orkut, and the AdWords interface.

"We've been working with those teams in applied R&D in the last year to evolve to meet their needs," said GWT product manager Andrew Bowers. Specifically, he mentioned three new features in the refurbished GWT:

• Speed Tracer, a Chrome browser extension that graphs a Web application's sluggishness over time.

The tool is designed to help Web developers find problems in the complex interactions of JavaScript, the Hypertext Markup Language (HTML) that's assuming new duties in describing a Web page, and the Cascading Style Sheets (CSS) that handle formatting chores. "As more functionality moves from standard JavaScript into HTML and CSS, a lot of things are moving to native functionality, it gets harder to find performance problems," Bowers said.

• "Code-splitting" technology to break Web applications up into urgent sections that must be downloaded immediately and the other parts that can be sent at a more leisurely pace.

Bowers likened the incremental application download feature to streaming video, where people can start watching the video before the full movie has been downloaded. The feature was developed with the Google Wave team, he added.

• Coming from work with the AdWords team is UiBinder, which lets programmers separate an application's user-interface code from the program logic that actually does the thinking. The result: user interface designers can be given free reign without the logic programmers worrying about everything breaking, Bowers said.

Google also has used GWT to develop Google Health and iPhone Web applications such as Google Latitude and Gmail.

But GWT isn't universal at Google. Google Docs and Gmail, for example, rely on JavaScript but don't use GWT. Some of those projects grew from code bases that predate GWT, Bowers said.

But Google is working pretty hard on another JavaScript programming tool called Closure, which has its own compiler to produce fast JavaScript. It's another open-source project, and not just a historical artifact.

Different strokes for different folks, said Bruce Johnson, GWT's technical lead of the different tools.

"Probably Closure is going to be more targeted at someone who wants to write JavaScript to begin with," Johnson said. "GWT is for Java developers or people who see additional benefits to programming that way."

Mozilla is wrapping up work on its first version of Firefox for mobile phones, an important step in bringing the second most popular PC browser to an area where a rival project holds more influence.

"Our goal is to have a release candidate next week," said Jay Sullivan, Mozilla's vice president of mobile. "If things go smoothly, we'll have a (final) version out in the next few weeks," with the debut planned for this year, he added.

Mozilla has been a leader in advancing the Web state of the art. But when it comes to the mobile phones, where the power of a new generation of hardware has transformed browsers from primitive afterthoughts to useful tools, Firefox has been missing in action.

Instead, an open-source project called WebKit powers the browser on the higher-end mobile phones du jour--Apple's iPhone, the Palm Pre, and Motorola's Droid and other models running Google's Android operating system, with BlackBerry headed that direction, too.

In contrast, the first mobile Firefox version will run on Nokia's powerful but relatively obscure new N900, a $569 hybrid computer and mobile phone that uses Nokia's Linux-based Maemo operating system. A Windows Mobile version of Firefox is set to arrive next year, and Mozilla has begun working on an Android version now that Google released a native developer kit.

Firefox has one big thing going for it, though: it's a close relative of the PC-based browser that today is used by about a quarter of people on the Web.

The link extends beyond brand familiarity. For one thing, mobile Firefox is based on the same code as the present Firefox 3.6--also a beta version due to finished by the end of 2009. For another, through a Mozilla service and browser plug-in called Weave, mobile Firefox synchronizes bookmarks, passwords, and even open tabs with the desktop version of the browser.

In addition, Firefox for the N900 can run many Firefox extensions--AdBlock Plus among the 30 or so now available. Sullivan recommends updating their interfaces for the small devices, though.

Nokia partnership
Mozilla has been working closely with Nokia to develop Firefox on its N900 handset. It already ships with a lighter-weight browser that uses the same Gecko code base as Firefox, but the full Firefox mobile version--a project code-named Fennec--is more powerful.

"You want to put the desktop experience into a pocket-sized device," said Ari Jaaksi, vice president of Maemo devices. "What do people use on the desktop? Firefox."

However, Firefox won't ship with the device, at least initially. The company is open to the idea of including it in the next version of the operating system, due in the second half of 2010, Jaaksi said. Mozilla, meanwhile, is comfortable with the idea of people having to actively download the browser, the most common way Firefox has been distributed on PCs.

The N900 is available as an unlocked device through various retail channels, but Nokia doesn't yet have any partnerships in the United States with wireless service carriers who might help bring the N900 to a broader market. It's a relatively powerful device with a 600MHz processor and 3D graphics hardware--enough oomph to run Adobe Flash on Web pages today. Its price may seem high, but bear in mind that unlocked devices don't get a subsidy by carriers that expect to see their up-front payment returned over months of subscription payments.

Nokia's N900 will be the first device that runs the mobile version of Firefox.

(Credit: Nokia)

So does Firefox require this level or horsepower?

"We need pretty high-end stuff to make the Web great," Sullivan said, but not so high-end that the N900 is the only handset to fit the bill. "Everything now on the mid- to high-end is fine."

WebKit has intercepted the newer generation of smartphones. Through the wonders of Moore's Law, new devices get steadily more processing power and memory. So aiming for today's top-end phones can mean software will work on tomorrow's mainstream models.

The N900 is at the top end of the range, but Firefox runs elsewhere, too. The Windows Mobile version of Fennec is in alpha testing now, lagging the Maemo version by about three or four months, Sullivan said. Mozilla plans to release it in final form in the first half of 2010, he said.

Firefox: like an operating system?
Mozilla has a lot of plans for mobile Firefox that, to some extent, put it in opposition with Nokia. The N900 is aimed in part at programmers who want to low-level control over a device through its Linux operating system. But Firefox--like Google's Chrome--is assuming the role of a general-purpose foundation for running programs.

"We're almost an operating system," Sullivan said.

Several features support the direction. Built into Firefox now is geolocation, which lets a Web application tap into the phone's services to figure out where a user is and, for example, show a map of the nearest pizza shops. Also included is support for orientation detection, important for games, and offline data storage, important for a variety of programming needs.

There's more on the way in 2010, Sullivan said:

• Support for multitouch displays for a more sophisticated user interface.

• Support for haptic feedback, such as the phone vibrating when a virtual keyboard key is tapped.

• The ability to control a camera.

• Support for Electrolysis, Mozilla's project to split tasks such as the user interface, tabs, and plug-ins into separate processes. That improves stability and performance, he said.

• Support for JetPack, Mozilla's next-generation extensions system.

S• Integration of the Weave synchronization software so it's no longer a plug-in.

• Support for WebGL, an interface to provide browsers with accelerated 3D graphics.

• Faster execution of JavaScript programs that are common and increasingly powerful on the Web.

Applications that run natively on a device--whether directly on the hardware as in the case of the iPhone or on the Java-derived layer called Dalvik on Android--are an important area of mobile development today. But the Palm Pre uses a browser-based application design.

"It's the right model. It's not there yet," Sullivan said of Web-based programs. Today programmers must create separate versions of applications for BlackBerry, Nokia's Symbian, Android, the iPhone, and other mobile phones.

But that profusion will be replaced by the universality of the Web, he predicted.

"In three years," Sullivan said, "80 percent of those applications are going to be Web-based."

The beta version of Chrome for Mac OS X is available. Google released its browser beta for Linux too.

(Credit: Screenshot by Stephen Shankland/CNET)

Two key pieces of Google's effort to make Chrome a more competitive browser fell into place on Tuesday as Google released beta versions of the browser for Mac OS X and Linux.

Tuesday's software release is a version of Chrome that had previously been available only as developer preview software for Mac and Linux machines. "It took longer than we expected, but we hope the wait was worth it," product manager Brian Rakowski said in a blog post.

Macs are widely used, if not as common as Windows machines, and there's been some demand in tech circles for the Mac version of Chrome. Linux, while less widely used among ordinary computer users, has importance of its own: it's the foundation for Chrome OS. That's the browser-based operating system Google hopes will be popular on Netbooks starting next year.

According to the Chromium development calendar, the beta versions are scheduled to graduate to the next level of maturity, "stable," on January 12. Chrome for Windows graduated out of beta almost exactly a year ago.

Google doesn't emphasize product version numbers in the project, instead automatically delivering updates behind the scenes to the browser that take effect when it's restarted. But it does use version milestones to keep track of development internally.

The biggest new feature of Chrome 4.0 is support for extensions, which let people customize the browser. In the Mozilla world, they're called add-ons, and they've been a big part of Firefox's success.

Mac OS X has a mandatory menu bar, so unlike the Windows version, Chrome on the Mac has traditional menus.

(Credit: Screenshot by Stephen Shankland/CNET)

Extensions aren't useful, though, unless people can find them. Google on Tuesday also launched a Chrome extensions gallery page.

There are more than 300 extensions available for Chrome, extensions programmers Aaron Boodman and Erik Kay said in a blog post.

However, extensions on the Mac aren't yet available, though they had been for a time in the developer-preview version. "Extensions aren't quite beta-quality on Mac yet, but you will be able to preview them on a developer channel soon," Rakowski said.

Also on the Chrome for Mac to-do list: a bookmark manager, PDF viewing in the browser, bookmark synchronization, 64-bit support, and my personal favorite differentiator of Firefox 3.6 on the Mac, full-screen support.

Chrome now has an extensions gallery.

(Credit: Screenshot by Stephen Shankland/CNET)

Why try Chrome?
For those of you new to Chrome, here's a brief version of why it's my default browser on both Windows and, as of about a month ago, Mac OS X. Your preferences and needs may vary, of course, and I still use Firefox every day, too.

• Speed. It's fast to start up, though not quite as snappy as it once was now that it's not so bare-bones, and rivals are making progress. It's also fast loading Web pages and running JavaScript programs on them.

• Tabs. I spawn innumerable new tabs all day long, and when it takes a long time (I'm looking at you, Internet Explorer), I get infuriated. I also like the order in which new tabs arrive, a style Firefox is mimicking.

• The omnibox. It's a single bar that merges the utility of an address bar and search bar. I hit Ctrl-L (on Windows) or Command-L (on Mac) to pop my cursor up there, and start typing. One nice--if somewhat obscure--feature is fast site search on some domains, so for example I can type A, M, tab, and up pops an Amazon.com icon; what I type afterward is entered as a search on Amazon. That conveniently gets me straight to the search results so I don't have to see yet another Kindle ad.

• A minimal user interface. When browsing, I like my user interface to step aside and make way for the Web page. Scrolling was a wonderful innovation in computers a few decades ago, but I like to avoid it when I can. Chrome puts tabs in the real estate ordinarily devoted to a program's title bar and shuffles the menu controls off to the right of that tab strip (though the Mac version gets a regular menu bar).

Another potential perk: avant-garde Web technology, including WebGL and O3D for accelerated 3D graphics and Native Client for speeding up Web apps with direct access to a processor, are being built into Chrome. Another such Google project, Gears, is already built into Chrome--though Gears doesn't work on Mac OS X 10.6.

There are things you might miss--the full panoply of Firefox extensions, toolbars from Google or others, print preview. And the "browser not supported" error messages on various Web pages are annoying, though in my experience there's rarely an actual compatibility problem. Overall, I like it.

Is Google spying on me?
If you're worried about what new data Google will be able to harvest on you, I recommend a close read of Google's Chrome privacy page. This doesn't worry me much, but I may be insufficiently paranoid. In my opinion, the biggest thing is that Google stores 2 percent of the data it gathers when people type text into Chrome's combination search and address bar, called the omnibox.

That means Google can see not only what you're searching for (as it would for any Google search), but what Web site addresses you're typing as well. The data is anonymized within 24 hours, Google said.

Also, Chrome has a feature called DNS pre-fetching that tracks down the Internet server addresses on Web pages in anticipation that you'll be clicking links on the page. So Chrome--and Google, too, if you're using Google Public DNS--retrieves this information from the Internet.

Updated at 12:30 p.m. PST and 1:20 p.m.. Added further detail.

Opera Mini 5 and Opera Mobile 10 betas share a Speed Dial design.

(Credit: Screenshot by Jessica Dolcourt/CNET)

In mid-September, Opera surprised us with a redesigned Opera Mini beta browser for Java phones, including BlackBerry. It had tabbed browsing, a first for Opera Mini, and Speed Dial, a carryover interface from Opera desktop browser (Windows|Mac) that you encounter each time you start the browser or open a new tab. Two things it didn't have: a download manager and Opera Link, the account-based tool that syncs bookmarks, Speed Dial options, and browsing history among your Opera browsers. With it, Web surfers can quickly get to favorite sites on their desktops, laptops, and smartphones.

On Wednesday, both Opera Mini 5 beta and the similar Opera Mobile 10 beta that followed it for Symbian Series 60 and Windows phones get an update that includes both Opera Link and a download manager.

These new beta builds aren't the first adjustment Opera has made to the redesigned betas. A previous tweak partially resolved a problem where Opera's mobile browsers weren't inputting the font style needed to render several Asian languages.

Plenty of other known issues still exist, including the browsers' tendency on Symbian phones to pop open a virtual onscreen keyboard when you flip the phone into landscape mode and start typing away on the phone's physical QWERTY, and the lack of support for non-touch-screen Windows phones. Opera provides a full list of known issues for Opera Mobile 10 beta here. I've also noticed that Opera Mini 5 beta rarely loads a page I've linked to from some other application on the BlackBerry I've been testing with. You may encounter the occasional bug as well in this not-quite-set beta release. If you find others, share them in the comments.

If you're curious how Opera Mini 5 beta and Opera Mobile 10 beta look and work, you can cash in on some instant gratification with this video. If you don't have a Symbian phone, don't let the fact that Opera is modeled on one in this video bother you--the builds are exceedingly similar for Java, Symbian, and Windows phones.

You can try the free cell phone browsers for yourself by pointing the mobile browser on your Java-based cell phone to http://m.opera.com/mini/next/. Download Opera Mobile 10 beta 2 for Windows Mobile and Symbian Series 60 phones by navigating to http://www.opera.com/mobile/download/.