We don't know much about the upcoming OS from Google, Chrome OS, so most of the news we read about it involves speculation or, sometimes, rather terrible attempts at faking some supposedly official screenshots. However, we recently stumbled on a tidbit of actual news that proves how tightly integrated the Google Chrome web browser will be with the operating system. Of course that makes sense - it is called "Chrome OS" - but it makes us wonder if Google will be required to support other web browsers on their new platform? After all, it's one thing to integrate your own browser with your OS (as Microsoft does with IE) but it's another thing to not even offer a choice. What will Google do? Will they go the "evil" route?

That's as much as we know for sure, but what is not clear is exactly how this SSO option will be presented to the user. We wouldn't be a bit surprised to see you logging into your computer with your Google account the way you log into your Mac or Windows PC using a set of credentials you create during the setup process. However, in Google's case, it's easy to imagine a more web service like prompt on the login screen. For example: "Create a Google account" / "Already have a Google account? Sign in here." Perhaps there will even be a "Remember Me" option so you don't have to log in again, you just flip the netbook's lid open. Of course that's all speculation, but it seems logical.

Will Chrome OS Offer Browser Choice?

The real question here is whether this SSO option will only work with the Chrome web browser which comes pre-installed on the new OS. Obviously, Chrome OS will push people to use Google's own browser, but will it be your only option? What if you really want to use Firefox because you've discovered you can't live without your add-ons and Greasemonkey scripts? Will Chrome OS's sign-in manager support that alternative? Will it - gasp - support IE8? What about Opera? Safari?

Microsoft has come under fire for "bundling" their web browser, Internet Explorer, with their operating system. In fact, the issue has led to the European Union's requiring that the company offer a "select your web browser" ballot screen in the Microsoft's new OS, Windows 7, due out this October. It would seem odd if Google could get away with not just bundling, but actually not even allowing another browser to install.

Although Google hasn't come out and said that will be the case, they've made no mention of how browser alternatives will be handled. In fact, when describing how their OS works, Sudar Pichai, VP Product Management and Linus Upson, Engineering Director, wrote: "the software architecture is simple -- Google Chrome running within a new windowing system on top of a Linux kernel." (In this case, "Google Chrome" refers to the web browser, not the OS. Oh, how we wish they had named them differently!)

What that means is that the very architecture of the OS depends on tight Chrome browser integration. While this is a revolutionary concept for building the OS of the future, to say the least, it begs the question: will Google get away with this? And finally, should they be allowed to?

Let us know what you think in the comments.

In PCMag tests, the Fennec browser was installed on two devices. On each one, the browser had to be launched twice in order for it to run. But upon start up, only the checkerboard pattern displayed, not the expected introductory screen with instructions. By scrolling up and left, you could reach the address bar, but entering in URLs only returned errors. By kick-starting the phone's modem by first launching Opera, it was possible to get the title bar of various web pages to appear - but still no page would display. Other Fennec testers experienced the same issues.

Wrote PCMag.com's columnist Sascha Segan, "If this is a milestone, it's marking a pit stop. Better luck next time, Mozilla folks."

What Happened?

According to Mozilla Mobile team member, Mark Finkle, the problem appears to be memory-related. He notes that Windows Mobile devices have some restrictions around memory use and that's what his team is now trying to work around. However, it sounds like the team still hasn't yet nailed down the exact problem which is causing the bug. On his blog, he writes "when we figure out the true cause...we'll be sure to blog the details." (When?)

Checking in on the bug's status, it's still listed as "Assigned to: Nobody." But we're taking that to mean (we hope) that the entire Fennec team is working on addressing this showstopper of an issue.

Says one commenter on Bugzilla, the problem happens immediately following an allocation failure in gfxImageSurface, but no one else has chimed in to confirm his statement yet.

The Mobile Web: the Next Browser Battleground

Interestingly enough, while Mozilla's attempt at the mobile web was crashing and burning, another mobile browser, Skyfire, was releasing a landmark version of their browser, too. Skyfire version 0.9 for Windows Mobile and Symbian, a browser which already supports Flash 10, Silverlight, and Ajax, introduced a new "social" version of their software on February 12th.

In the latest update, Skyfire offers a Friendfeed-like start portal which delivers news from RSS sources as well as updates from Facebook and Twitter. It's pre-configured with feeds from Digg, ESPN, Google News, Hulu, YouTube and Yahoo! News, but those can be easily customized.

In addition to relative newcomer Skyfire, some of the most popular browsers for the mobile web comes from Opera, whose mobile software is currently installed on millions of devices worldwide. 

Although Skyfire and Opera may not have the brand-name recognition that Mozilla enjoys (well, perhaps Opera does), it's clear that when it comes to mobile web browsers, innovation can happen anywhere, from any company. What dominates on the desktop will not necessarily be what dominates on our mobiles, and for mobile web users, that could be a good thing.

In parts of Africa, there simply is no mobile internet access available...but there is the ability to send SMS. Enter Mobile-XL. With their browser's graphical, easy-to-use interface, people with limited or no internet access finally have an entry point to vast resources of the web. The application, which works on Java-based phones with either GPRS or Bluetooth functionality, provides access to news, weather, flight status, package tracking, dictionary, thesaurus, translations, local 411, games, music, access to email, and more.

The XLBrowser doesn't have to be pre-installed on handsets in order for people to use it. If customers have a GPRS-enabled phone, they can text "XLB" to 3663 (for Kenya) or 7197 (for Uganda) or 3112 (for Tanzania). However, they will need a Bluetooth-activated PC or laptop to store the file that's downloaded from the link. The file then needs to be transferred to the handset using Bluetooth. For obvious reasons, having phones which are already equipped with the browser will give more people access to the mobile web, especially in places where PCs and laptops are hard to come by.

Says Guy Kamgaing-Kouam, CEO of Mobile-XL, "we're taking a gigantic step toward realizing our mission of bridging the digital divide." His company has been working since 2005 to develop a simple and affordable technology that could bring internet services to the underserved markets of the world.

The new partnership agreement between Nokia and Mobile-XL will deliver the XLBrowser in phones initially shipped to Kenya, Uganda, and Tanzania as early as March 2009.