Business Tech

Mozilla has updated its Firefox browser to patch three critical security holes.

Firefox 3.5.6 and 3.0.16 both fix earlier memory corruption issues. "We presume that with enough effort at least some of these could be exploited to run arbitrary code," the security advisory said.

In addition, the earlier version of Firefox 3.5 had two critical vulnerabilities in its technology for playing Ogg-format media, one with the liboggplay media library and one with the libtheora video library.

The patches are among 62 fixes in the new Firefox, software that's translated into dozens of languages and runs on multiple operating systems. Users of the OS/2 operating system will be delighted to know that problems with Firefox's full-screen mode and with print preview have been resolved.

"We strongly recommend that all Firefox users upgrade to this latest release," Mozilla said in a blog posting. By default, Firefox downloads updates automatically then prompts users to restart when it's ready; updates also can be retrieved through the "check for updates" menu option.

Mozilla plans to cease supporting Firefox 3.0 in January. Meanwhile, a significant update, Firefox 3.6, is due by the end of the year.

Correction 1:23 p.m. PST December 17: This story was corrected to note that it was the earlier versions of Firefox that suffered the vulnerabilities.

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.

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."

Mozilla, determined to release Firefox 3.6 before year's end, is also determined to squeeze as many features as possible into the new browser.

The latest example: support for the File interface that adds more sophistication to uploading and some other chores.

Support for the feature is one of the 133 changes that arrived in Firefox 3.6 beta 4, which the Mozilla project released Thursday for Windows, Mac, and Linux.

The File API (application programming interface), a draft standard at the World Wide Web consortium, lets browsers handle files better. Among its abilities are uploading multiple files at once, showing thumbnail previews of images that have been selected for upload, breaking a long video upload up into chunks to protect against network interruption problems, and integrating with drag-and-drop Web applications.

While many software projects use beta testing periods to shake down their code, Mozilla isn't afraid to add new features as it goes. That can mean new ideas arrive sooner, of course, but it also can delay the completion date of the new version. What was to have been a quick Firefox 3.1 release was pushed back months as new features were added and the version ultimately was renamed Firefox 3.5.

For those who want to dig into the File interface, Mozilla offers a Web developer guide to using it.

The beta-testing periods aren't just important for debugging Firefox itself. New versions often don't work with older add-ons that people install to customize the browser, so beta testing gives some time for programmers to update those add-ons. Mike Belzner, Mozilla's director of Firefox, said 70 percent of add-ons are now compatible with Firefox 3.6.

Sometimes it's the little things that count.

The most prominent feature of Firefox 3.6 is Personas, which let you reskin the browser with thousands of different looks. But my single favorite change is a subtler change to the open-source browser's user interface.

Specifically, when you open a link in a new tab, it appears immediately to the right of the active tab. Before, the new tabs would appear to the far right of the strip of tabs.

Yup, that's it. For those of us who spend hours a day in a browser, though, the new tab behavior helps group related tasks together. I constantly shuffle among dozens of tabs, and the new approach automatically brings some organization to my cluttered life.

However, I know it's not everybody's favorite browser behavior. So along with explaining why I like it, I'll also take some potshots and share instructions on how to get the old way back.

Why it's better
The more things I do with a browser--and the number has increased steadily for years now--the more important it becomes to be able to find different tasks amid the chaos. Microsoft and Apple understand this, as evidenced by the new taskbar features in Windows 7 and dock expose in Mac OS X 10.6, aka Snow Leopard. Those features make it easier to pluck out the one window you need from among the many you may have open.

There's a pattern to how I spawn the dozens of tabs I use as a day progresses. On a variety of pages--Gmail, Google Reader, Yahoo Finance, somebody's blog post--I'll encounter a host of links to other pages. I'll middle-click my mouse button to open interesting pages as background tabs, then use Ctrl-Tab to switch to the new pages when I'm ready. I repeat this pattern many times a day.

With the old behavior, each tab appeared to the far right of the tab strip. That's fine when getting started, but when I've moved halfway across the list and want to open another batch, I want the new ones--call them children--to open next to their parent tab. When I go away and come back, or when I lose place juggling tasks, it's easier to find my bearings again.

It's like being in a library. When you're in the European history section, you don't want to find books on rewiring your house and on vegetarian cooking.

As a longtime Firefox user, I didn't realize tab positioning could be better. When I started using Google's Chrome, which introduced the new tab behavior to me, the scales were lifted from my eyes. I immediately could get to the next tab with a quick press of Ctrl-Tab on the keyboard rather than have to use the mouse to click over to the far end of the list. I use both browsers daily, but until the Firefox 3.6 beta arrived, the new-tab position had become a sore point for me when in Firefox.

The change is actually a big deal in a couple ways. First, even seemingly minor changes in software can be disruptive. Old habits die hard, and computer users wrestling with constant change can get angry when more is foisted upon them.

Second, though, browsers are assuming an ever greater role in what people do in their personal and professional lives, and keeping one's bearings is commensurately important. That's especially true for those people for whom a gaggle of browser tabs represents a collection of chores going on in parallel.

Internet Explorer 8 categorizes related tabs by color.

(Credit: Screenshot by Stephen Shankland/CNET)

How the competition handles it
Tabs are now universal among browsers, but new-tab behavior isn't. Firefox and Chrome handle it the way I like best, but how do others tackle the issue?

First, let's look at Internet Explorer 8. Microsoft showed it understands some of the challenges of tab management in its latest version of its browser by coloring child tabs the same hue as their parents, but I have a gripe with how it works. Specifically, although child tabs get the same color as their parents for easy grouping and arrive to the right, grandchild tabs are the same color as child tabs. Similarly, grandchild tabs appear to the far right of the whole group of child tabs.

In my mind, I consider grandchild tabs a separate group from the child tabs. But with IE, grandchildren get the same color and position treatment as children. The only way to get a new color is to start a fresh empty tab There's no easy way to give grandchildren a new color without causing some confusion, though--should the child be the same color as the original parent or change color to be grouped with the grandchildren?

Next is Opera, which gives users a choice. By default, it opens new tabs to the far right, which I don't like, but in the Advanced|Tabs section of the preferences dialog box, you can check "Open new tab next to active." Huzzah!

There's a subtle change here I don't care for, though. Tabs always appear immediately to the right of the active tab. I'd rather have all one tab's children appear in sequence to the right. For example, if a parent tab is in position 1, then the first child would be in position 2, the second in position 3, and the third in position 4. Opening three child tabs in Opera leaves the parent in position 1, the third child in position 2, the second child in position 3, and the first child in position 4.

Last, there's Safari. It does it the old way I loathe with no option to change. Too bad.

Firefox can show thumbnail previews of new tabs, but I find them hard to recognize in front of busy Web pages.

(Credit: Screenshot by Stephen Shankland/CNET)

Why it's not enough
Most browser makers are excited about the fact that their software is subsuming more and more computing tasks that previously ran on computer operating systems. But as browsers inherit this central importance, they also inherit some of the hassles.

The new tab positioning behavior in Firefox is a step in the right direction, but there's more that needs to be done. Moving from one tab to a related adjacent one, whether through a keyboard command or mouse clicking, is a minor change. But things get harder when you need to switch from one group of tabs to the next.

There's work under way here. Opera is perhaps the leader with the ability to show thumbnails as you use Ctrl-Tab to cycle your list of open tabs.

Firefox has been noodling with the approach too. It tried then dropped tab thumbnail previews earlier, but the technology is still present. Using the about:config system for tweaking the browser (more on this later), you can change the "browser.ctrlTab.previews" setting to "true."

But for reasons that aren't clear to me, I don't find this effective either in Firefox or Opera. Perhaps I haven't used it enough, or the thumbnails are too small to be immediately recognizable, or they're just hard to see against the noisy background. There's a good reason that Apple dims the background most of the way to black when using Expose.

Aero Peek in Windows 7 lets the task bar show a glimpse of Firefox and IE tabs.

(Credit: Screenshot by Seth Rosenblatt/CNET)

Windows itself is helping, too. The new taskbar in Windows 7 can show individual tabs, once browsers support the feature. It's in Internet Explorer 8, and it's in the new Firefox 3.6 beta.

Add-ons such as Firefox Showcase can further tweak Firefox. (Indeed, for a wealth of options, check Mashable's handy Firefox tab management guide.)

More interesting to me, though, is work under way to expand Firefox's "awesome bar" abilities. Today, typing in it opens Web pages and retrieves ones you've already visited or bookmarked. In the future, it could be able to move you to another open tab, too. I'm a keyboard guy, so particularly appreciate this idea.

You can get a taste of the idea now. If you've enabled the "browser.ctrlTab.previews" option, hitting Ctrl-Shift-Tab will not only show you thumbnail previews, but will put a cursor in a search box.

Typing the letters of the Web page name will winnow down the thumbnails. For example, typing "netap" will cull my open tabs so only Net Applications and NetApp show. If you have a bunch of similar tabs all open, this might not help much, of course.

However, the feature only works with the tabs of one browser window, so if you can't use it to search among other browser instances.

How to get the old way back
Perhaps I've convinced you that the new approach is better. But perhaps not--in which case I encourage you to share your thoughts in the comments so people will hear more than my opinion.

For those who don't like the new tab positions, you can revert to the old method.

To get the old style back for new tab position, use Firefox's about:config system.

(Credit: Screenshot by Stephen Shankland/CNET)

First type "about:config" in the Firefox address bar. You'll get a warning that you're tinkering with Firefox's innards and you should be careful, but this isn't brain surgery, so don't be frightened. Click the "I'll be careful, I promise" button, and you'll see a big list of all the browser settings that can be tweaked.

Next, in the text box labeled "Filter:", type "tabs.insertRelatedAfterCurrent"; you should see just one entry below. In the column marked "Value," double-click on the word "true" to change it to "false." You're done.

But I'd encourage you to at least give the new way a try. If you don't like it, you can always change back.

The World Wide Web Consortium has published a draft of an interface that browsers can use to manipulate files better, one of a series of steps aimed at gradually improving the sophistication and polish of Web site interfaces.

The draft File API (application programming interface) defines a number of ways that browsers and Web sites can handle files better. One big part of it: being able to select multiple files for upload, such as on photo-sharing sites or Web-based e-mail, a task that often relies on Adobe Systems' Flash today.

But there are other aspects, too. For example, the Files interface governs the use of "blobs," or packages of raw binary data such as video files. Google has touted blobs for its Gears browser plug-in as a way to divide large videos into small chunks so that uploads can be more easily resumed if a network problem interrupts the process.

Another benefit: files are handled asynchronously, which means the browser won't freeze up while a file is being uploaded or otherwise handled, and the browser reports progress on file transfers.

The technology is one example of work to transform the Web into a better foundation for interactive applications, a move that usurps some power from computer operating systems such as Windows and that's embodied most boldly in Google's Chrome OS project.

Here's one example of use of the Files interface provided by Mike Smith, who works for the W3C on matters relating to HTML--Hypertext Markup Language, the language used to describe Web pages:

A user uses a Web-based application for reading and sending e-mail. She wants to attach multiple files to particular messages. The Web application provides an user interface that allows her to select multiple files to attach at the same time. After she selects the files, they are uploaded to the Web application asynchronously, allowing the user to perform other actions while they are uploading (for example, finishing the rest of the message she was composing before you added the file attachments). As the attachments are uploaded, the Web applications shows progress bars to indicate how much of the contents of the files have uploaded thus far.

The interface can work in conjunction with various standards including the drag-and-drop support in the HTML 5 now under development and the Web Workers technology that lets browsers better perform multiple operations simultaneously.

The interface also can help Web applications process the contents of files. For example, Smith describes a lyrics finder:

A user has on her local file system a playlist file from her favorite desktop music player. The playlist contains a list of song titles and information, and she wants to be able to easily fetch the lyrics for particular songs without needing to manually search for the lyrics on the Web. So a site can provide a Web-based application that allows her to upload her playlist. The Web application then parses the file and then presents a user interface to her, show in the contents of the file as a hyperlinked, sortable list. She can then retrieve the lyrics for any given song just by clicking on a particular song title.

Arun Ranganathan, Mozilla's standards evangelist and chairman of the WebGL working group, wrote the specification, according to Chris Blizzard, Mozilla's director of developer relations.

Standards for the Web are advancing rapidly with W3C representatives including Microsoft working in conjunction with a parallel effort, WHATWG. New standards require actual implementation in browsers before they are accepted as finished, a fact that can lead to some chaos but that helps ensure the new ideas are tested in the real world.

Firefox 3.6, in beta testing now, will support most of the Files API, according to Blizzard.

Last week, Microsoft showed off some browser technology that could help Internet Explorer leapfrog the competition. But if Mozilla succeeds in its hope, Microsoft could be playing catch-up instead.

The technology in question is hardware-accelerated graphics and text using interfaces called Direct2D and DirectWrite that provide an easy way to use graphics cards' computing power. They're built into Windows 7, and Microsoft is bringing them to Windows Vista but not Windows XP.

The performance boost from Direct2D and DirectWrite was the centerpiece of Microsoft's demonstration of Internet Explorer 9 goodies shown last week. Online maps flashed on the screen quickly and tracked mouse movements responsively; text was clearer and changed sizes more gracefully.

But the day of Microsoft's demo, Mozilla evangelist Chris Blizzard had this to tweet: "Interesting that we're doing Direct2D support in Firefox as well--I'll bet we'll ship it first."

There's work to back up his rhetoric. On Sunday, Bas Schouten, the programmer who's been leading the work for Mozilla, posted a prototype of Firefox using the Direct2D and DirectWrite.

However, any Firefox fans tempted to crow about a victory should be cautious. Mozilla wouldn't commit to including the technology, much less to a release schedule such as Firefox 3.7 due in the first half of 2010. "We are currently investigating Direct2D for Firefox, but do not have a target for shipping it in Firefox at this time," the organization said in a statement..

Several Web pages arrive significantly faster using Direct2D rendering technology in Firefox.

(Credit: Bas Schouten)

The race is on
Microsoft declined to comment for this story, referring readers just to last week's blog post about coming Internet Explorer 9 features. "While we're still early in the product cycle, we wanted to be clear to developers about our approach and the progress so far," the company said while sharing a Direct2D demonstration video.

There's no doubt the race is on, though, given the potential benefits of the new interface and the commercial success of Window 7. Microsoft is lighting a fire under its developers, but the company's browser has lagged Firefox and other rivals in many technological areas for years, and many Web developers loathe earlier versions of IE still widely used. IE's market share has steadily eroded, though it remains dominant overall.

The attention is giving Google ideas, too. In a Chrome issue logged Sunday, Chrome programmer Peter Kasting pointed to Schouten's blog post on the subject as "motivation."

"If we can speed up the rendering time, the most noticeable benefit will probably be smoother-feeling scrolling," Kasting said. He also directed attention in October to DirectWrite support in Chrome, though cautioning that it might not work with the browser's present "sandbox" design to isolate elements of the browser for security reasons.

Mozilla has its own results to show off, too. Schouten offered a graph showing improved performance displaying a variety of Web pages. Facebook, Google, and Twitter rendered on the screen in half the time using the Direct2D; Slashdot and a Wikipedia entry were barely changed. One taxing page using the Scalable Vector Graphics format (SVG) to show movable, resizable graphics showed more than twice as fast, dropping from about 11 milliseconds to less than 4 milliseconds.

Microsoft's DirectWrite permits smoother display of many fonts.

(Credit: Microsoft)

What actually changes?
Direct2D replaces an older technology called Graphics Device Interface (GDI) used in Windows XP. Both offer a way for programs to tap into computing hardware without having to worry about the particulars of video card capabilities and settings, but Direct2D taps into hardware acceleration features.

The technology lets programmers control basic elements such as transparent boxes, curved lines, and resizable photos. Out of these, user interface elements are constructed; Direct2D calls upon a computer's graphics processor to speed that up. It's particularly helpful for dynamic situations that change element properties such as color, size, or opacity.

DirectWrite offers a similar graphics chip boost to the task of displaying text. That may not sound computationally intense, but some parts of it are. In particular, DirectWrite offers a more sophisticated mechanism for displaying text to take advantage of something called sub-pixel positioning of letters.

Each pixel on an LCD screen is actually made of three tiny slices--for red, green, and blue components--and sub-pixel technology subtly draws letters using pieces of these pixels to make the overall appearance smoother. The older GDI permitted some sub-pixel positioning, but only smoothed letters in the horizontal direction; DirectWrite smooths curves vertically as well.

Using the graphics chip in Direct2D and DirectWrite operations brings several advantages. Performance is the first: some operations are faster or smoother, and having more power on hand lets programmers tackle more ambitious projects. Second, the general-purpose central processor, relatively inefficient at handling graphics tasks, is unburdened, freeing it up for other tasks and saving battery power.

Firefox already has a graphics system of its own called Cairo. Schouten has been adding a Direct2D and DirectWrite.

Firefox is of course a browser that doesn't just work on Windows. The DirectWrite technology helps that operating system catch up to its rivals, said Mozilla's John Daggett in a blog post Sunday. "Platform APIs [application programming interfaces] on Mac OS X and Linux already do a good job rendering Postscript CFF [Compact Font Format] fonts," he said. "This just brings them up to parity under Windows 7."

Direct2D is used elsewhere in the browser. "We've made significant progress and are now able to present a Firefox browser completely rendered using Direct2D, making intensive usage of the GPU," or graphics processing unit, Schouten said. And because Cairo is used by other open-source software, other projects will benefit from the work, he added.

The Direct2D work is Mozilla's second hardware acceleration effort; the company also is working on one using a different hardware acceleration interface called OpenGL for mobile devices using Nvidia's Tegra chips, according to Mozilla.

This Mozilla demonstration of photos and Scalable Vector Graphics (SVG), with transparency and click-and-drag resizing, works more than twice as fast Direct2D graphics.

(Credit: Screenshot by Stephen Shankland/CNET)

The interactive Web
Microsoft went out of its way to emphasize that the Direct2D and DirectWrite work will help existing Web pages without programmers having to change a line of code. Dean Hachamovitch, general manager of Internet Explorer, contrasted that to other hardware acceleration efforts including Native Client and O3D from Google and WebGL from Mozilla and the Khronos Group.

Native Client, O3D, and WebGL are part of a long list of developments designed to transform the Web into a foundation not just for static pages but also for interactive applications. Those technologies, though, require new programming skills and tools.

Mozilla, Google, Apple, and Opera have been pushing this interactive Web agenda, and Microsoft is showing signs of interest, too. However, for now, Microsoft emphasizes that Direct2D support will help the existing Web. But the browser makers have their eyes on interactive technology as well. Direct2D will help with complex sites that use 2D graphics interfaces such as SVG and Canvas, Mozilla said.

Added Schouten, "As Web sites become more graphically intense, dynamic graphics will start playing a larger role, especially in user interfaces."

Google wants to catalyze the era of Web applications with its Chrome OS project, but Mozilla has no plans for its own browser-based operating system, at least for now.

"We're really focused on making the Web the right platform of whatever operating system one is using. That's a fair amount of work," Mozilla Foundation Chairman Mitchell Baker said. "I think we're going to continue to focus for quite awhile on the Web itself as a platform and the capabilities of the Web rather than build an operating system of our own and pull everybody into our world."

Mozilla Foundation Chairman Mitchell Baker

(Credit: Mozilla)

Baker shared the thoughts in an interview about the Mozilla Foundation's report of $79 million. The foundation isn't strapped for cash, but it is financially tiny compared to the three main rivals in the browser market today, Microsoft, Apple, and Google.

Microsoft was largely dormant when Firefox was getting its start five years ago, but the company is lighting a fire under its Internet Explorer developers for IE 9. Among the features the company touted are faster execution of Web-based JavaScript programs, better compliance with Web standards, and higher performance in general.

Internet Explorer remains the dominant browser in use today. Today, the elderly IE 6, dating from 2001, still is the most widely used version, and its widespread use is an anchor that keeps Web developers and therefore other browsers from advancing as fast as they might. So, unsurprisingly, Baker was comfortable with the prospect of a higher-powered IE being resurgent.

"If it could resurge enough to pull the hundreds of millions of people still using IE 6, we'd all be ecstatic," she said. "A lot of people are going to continue to use IE. They get it on their machine. If Microsoft makes that product more capable so the Web can move forward, there's good in that."

The Mozilla Foundation, of which Firefox developer Mozilla Corp. is a taxable subsidiary, gets the bulk of its revenue from Google through a search-ad deal that runs through 2011 at present. Search traffic that stems from Firefox's built-in search bar is set by default to go to Google, and a portion of the resulting Google search-ad revenue goes back to Mozilla.

Mozilla is looking to diversify its revenue sources, though, Baker said, and has taken some small steps.

"We did some small diversification in search, for example in Russia," using Google rival Yandex's services, she said. "We look at diversification, but we're not rushing into it."

And she's comfortable with today's funding situation because it doesn't force Mozilla to take Firefox in a direction it doesn't want to go.

"We have search in the product because we want it. We don't have any other discussions with Google about what the product is," she said. "The search and revenue relationship is completely distinct from the product development relationship."

Though Mozilla's revenue grew only at 5 percent from 2007 to 2008, compared to 12 percent the year before, Baker isn't concerned. "It matches our projections" of slow, steady growth, she said. "We're pretty much in line."

Digging into the financial statement, it should be noted that the foundation's $79 million in revenue is after a $7.8 million unrealized loss in the value of its investments. As the economy improves, it's possible those investments will recover some of their value.

The foundation is making more money than it loses. Expenses were $49 million for 2008, according to the financial statement.

"We have adequate resources to do what we have planned, plus save a little bit," Baker said. "Right now we're not bumping up against the ceiling. Our revenue is adequate to meet our needs. We try to be careful with money."

The Internal Revenue Service is scrutinizing Mozilla's corporate structure--a foundation with two taxable if not exactly for-profit subsidiaries. The foundation disclosed the scrutiny a year ago, and that investigation is continuing, Baker said.

"The IRS can be a very slow-moving organization. It's still an open discussion," she said, and the foundation is taking the matter seriously. "We don't have a clear idea what the IRS is thinking."

Two years ago, the Mozilla Foundation established its second taxable subsidiary, Mozilla Messaging, which focuses on the Thunderbird e-mail software and more recently on the Web-based Raindrop universal communications service. For now, that project gets its funding from the Firefox side of the house, but Baker plans to increase its financial focus once the near-final Thunderbird 3 is finished.

"The task now is to ship first Thunderbird 3. We expect to see that this year," Baker said. Mozilla overall is set up to be sustainable, not to be a money machine, but Mozilla Messaging will need to generate more revenue on its own eventually to help with that sustainability effort.

The Mozilla Foundation's revenue grew 5 percent to $79 million in 2008, with its Firefox search-ad deal with Google still the biggest benefactor, the organization said Thursday.

The figure is notable for an open-source effort, but the growth tapered off significantly. For 2007, by comparison, the Mozilla Foundation reported $75 million in revenue, a 12 percent increase over 2006.

Mozilla Chairman Mitchell Baker revealed the latest Mozilla figures on her blog Thursday.

Update: for further details and commentary from Baker, check this follow-up interview.

Firefox has won over about a quarter of the world's users of Web browsers, taking most of that share from Microsoft's still dominant Internet Explorer. The browser faces new challenges, though, in the form of newcomer Google Chrome and Microsoft's resurgent effort to improve Internet Explorer. On Wednesday, Microsoft showed off some elements of the forthcoming IE 9, and Thursday, Google released the source code underlying its Chrome OS, a browser-based operating system for lower-end computers.

Google supplies "the bulk" of the Mozilla Foundation's revenue through a deal that currently lasts through 2011, the foundation said. Under that deal, people performing searches through Firefox using the default Google search engine see and sometimes click on search ads at Google; Google and Mozilla share the resulting revenue. In 2007, Google supplied 89 percent of Mozilla's revenue.

Google isn't the only revenue source, though. Here's how Mozilla described its sources in an FAQ:

"The majority of this revenue is generated from the search functionality in Mozilla Firefox from partners such as Google, Yahoo, Amazon, eBay, and others. Mozilla takes in additional revenue from donations, online affiliate programs, the Mozilla Store, and income on our invested assets. In 2008, we expanded our Firefox partnerships with new firms such as Yandex (Russia Search), Canonical (Ubuntu), and Nokia (Mobile).