ReadWriteWeb

Catching up to Chrome is just part of the Firefox roadmap for 2012. Mozilla's Asa Dotzler has updated the strategy and roadmap for desktop Firefox in 2012. While the Mozilla folks have several original ideas and goals, there's a lot in the first half of the 2012 roadmap that looks very familiar to Chrome users as well. The really interesting features come in the second half of 2012, and relate to user privacy and account management. Third party cookie management and tracking could be a killer feature for Firefox later this year.

If you have a look at the desktop feature roadmap, you'll see that Q1 and Q2 have quite a few features that are either already in Google Chrome. For example, there's sync for add-ons, assuming add-ons work across releases, silent update and a redesigned new tab page.

Mozilla's Dietrich Ayala would like to have one million contributors to Firefox in 2012. It's a tough, probably unreachable, goal that Ayala says he's kidding about. Kind of.

Ayala spoke at FOSDEM about developing Firefox in 2012, and new approaches that Mozilla is taking to try to reduce time and effort required for contributing to the browser.

The latest stable release of the Firefox Web browser is on its way. Firefox 10 will emerge from beta with a few new features, most of which are geared toward developers. As is often the case, the new version pushes forward with a few of the latest features in emerging Web standards like CSS3, HTML5 and related technologies. In Firefox 10, it's more about the under-the-hood stuff than the on-the-surface user experience.

Some of the more significant enhancements include a full-screen API for Web apps, support for CSS 3D transforms and an improved handling of plugins and how they're updated.

If you're one of the few Firefox users still on Windows 2000 or still using Windows XP without Service Pack 2 or later, Firefox is going to have to say goodbye. Yesterday, Mozilla's Asa Dotzler announced that Firefox team is moving to a newer version of the Visual Studio toolchain. Once Mozilla moves to Visual Studio 2010, they won't be able to build for Windows 2000, XP RTM or SP1.

The SOPA/PIPA blackout today by Wikipedia, Mozilla, WordPress.com and many other sites is (I hope) drawing attention to proposed legislation that is considered a threat to "Internet freedom." That's fine, admirable, and (with any luck) will be effective at curbing SOPA/PIPA for at least another legislative season. The backgrounders I've read so far by Wikipedia and others explain pretty well why SOPA/PIPA shouldn't pass. What they don't say is that SOPA/PIPA are business as usual, and the protest is a last-ditch effort necessary because the legislative system and mainstream media are fundamentally broken.

Mozilla has some big plans up its sleeve in 2012. The non-profit open source foundation is planning some features for its Firefox Web browser and beyond that will require greater access to user data. In a blog post, the organization explains exactly how it intends to use and handle that data. In short, very carefully.

Some of Mozilla's initiatives for this year include an HTML5 Web app store, a mobile operating system and perhaps most intensive of all, a decentralized system for user identification and authentication at the browser level. In other words, a browser-based replacement for usernames and passwords.

As beloved as Firefox is by its users, the open source browser has had a harder time finding hardcore fans among IT managers at large companies and other organizations. That's because its rapid release cycle has always been notoriously tricky for them to keep up with. On top of that, Mozilla would sometimes end support on a particular older version of its browser before enterprise clients were ready.

Mozilla has heard the pained cries of IT managers everywhere and today announced that they're going to put out an Extended Support Release version of Firefox to help organizations better manage and support the software.

Google and Firefox renewed their partnership last week, ensuring that Google will remain Firefox's default search engine (and major source of revenue). Kara Swisher reported that the deal brings in just under $300 million per year for Firefox, amounting to almost $1 billion total. Google has to cough up the cash to prevent this coveted spot in the popular browser from going to Bing and Microsoft.

MG Siegler wondered why Google would bear this expense, "paying all that money to a competitor." He considered whether antitrust concerns played into the decision, or whether it was about mobile dominance. But Chrome engineer Peter Kasting offered a simpler answer today: "Google is funding a partner," not a competitor.

Well, 2011 didn't see the beginning of the end of Firefox after all. That is, Google renewed its agreement with Mozilla, ensuring the nonprofit's popular browser wouldn't lose 84% of its revenue and thus face the ominous fate that some predicted and others decried as unrealistic.

The browser was knocked from its #2 slot behind Internet Explorer, though, at least according to one company's stats. The culprit? Google's Chrome, a browser half Firefox's age.

Last year Xmarks, the cross-platform bookmark sync service, narrowly escaped being shut down for good. After tons of media attention focused on the shutdown, and then acquisition by LastPass, a funny thing happened – the service received almost no attention at all in 2011. So whatever happened? I caught up with LastPass CEO Joe Siegrist about the features added to Xmarks this year, the fate of the original Xmarks team and what he calls anti-competitive behavior on Apple's part.