Browsersphere

When I mentioned this Firefox Mobile video in the last issue of Around the Browsersphere, I also mentioned that it was a little lacking in the hands-on details department.  Little did I know at the time that testing out Fennec (the codename for the Firefox Mobile browser) was so simple to do.

Fennec, which is currently at version 1.0 alpha 1, or also referred to as M9 (a user experience alpha),  can be installed on Windows, Linux and Mac, in addition to its intended target, the Nokia N810 Internet Tablet.  To do so, simply grab the zip file or distributable associated with your OS.

I installed Fennec on Windows 7 to check it out, and the simulation works pretty well.  You can see how pages are rendered according to the smaller screen size, and you can also get a feel for how close the rendering of the page is to what you see in your normal desktop browser.  One of the things that stood out in the aforementioned YouTube video was the fact that all of the controls are hidden off to the sides of the page.  You simply “swipe” left or right to access the currently open tabs and navigation/settings, respectively.

The following is a look at Browsersphere loaded up in Fennec:

And here’s a look at ESPN.com loaded with the currently open tabs displayed off to the left:

And finally, here’s a look at the Fennec release notes page with the navigation and settings icons off to the right:

Obviously, you can’t get the best feel for what Fennec will feel like running on its intended hardware by running it on a dekstop OS, but you get a general idea for the layout of the controls, the way the pages render, etc.  Overall, I got a good impression from my quick look at Fennec, and it sounds like others have been impressed as well.

If you’re as curious as I was about how Fennec compares to some of the other mobile browsers out there, I’d recommend installing it on your desktop computer and giving it a try for yourself.

Tags: Alpha, Fennec, Firefox Mobile, Linux, Mac, Mobile, Mozilla, Nokia N810 Internet Tablet, Screenshots, Videos, Windows

A post at Tombuntu uncovers the fact, for me anyway, that there is a pre-alpha version of Chromium already available for use on Linux.  The following is an excerpt of the author’s review:

Chromium for Linux is pre-alpha software, but farther along in development than I expected. The GTK-based Linux interface looks and works just like Windows interface. The browser rendered sites I tested it with just fine, and I haven’t been able to crash the it yet. Lots of features, such as bookmarks, the options window, and even the about window, are simply…not implemented yet.

The review goes on to say that the tab bar is also missing, making it difficult to do anything with tabbed web pages, but that, like on the Google Chrome Windows counterpart, each tab runs in its own process.

Apparently getting the pre-alpha build is as simple as issuing the following from the command line:

sudo apt-get install chromium-browser

You can read much more about the Chromium build(s) in question over at Chromium on Ubuntu.

Hap-tip to Lim Chee Aun.

Tags: Alpha, Chrome, Chromium, Google Chrome, Lim Chee Aun, Linux, Reviews, Ubuntu, Windows

Anyone who has followed the support for web standards in today’s popular web browsers knows that the WebKit rendering engine has been at the forefront of that support.  Therefore, if you’re a browserphile like me, there’s a good chance you’re interested in testing out the latest and greatest WebKit build so you can see what all the fuss is about.  The following is a step-by-step list of things I had to do to get WebKit nightly builds working on my Windows computer.

1. Download and install the Safari web browser for Windows.
2. Download the latest WebKit nightly build for Windows.
3. Unzip the contents of the download to a location like C:\Program Files\WebKit Nightlies.
4. In the contents of the extracted folder, run (either from the command line or by double-clicking on the file) run-nightly-webkit.cmd.
5. Watch as several necessary files are copied over to your Safari installation directory.
6. If Safari launches and then crashes, fear not.  First try running the run-nightly-webkit.cmd file again.  If the crashing persists, work backward through the Windows Nightly Build Archive until you find a working build.  Remember, nightly builds are almost always considered dangerous (which is why the Firefox nightlies are called “Minefield“) so it may take some tinkering around before you find a good one.  The last good one I found at the time of writing was r34388.
7. If Safari launches and renders the default start page, you’re in business.

If you want to verify that you’re indeed using the WebKit nightly build you downloaded and not the default Safari rendering engine included with the latest version (3.1.2 at the time of writing), an easy way to check is to head on over to the Acid3 test.

This is what the test looks like in Safari 3.1.2:

And here is what it looks like in WebKit nightly build r34388:

Pretty cool!

I’d be remiss not to mention Swapnonil Mukherjee’s previous post on the subject, which proved to be a pretty good guide to getting a WebKit nightly build running on my computer.

Tags: Acid3, Development, Firefox, Minefield, Nightly Builds, Rendering Engines, Safari, Screenshots, Testing, Unreleased, Web Standards, WebKit, Windows

Hot on the heels of Firefox 3 potentially being released, I noticed (via Twitter again) that the Flock team has made Flock 2.0 Beta 1, which is based off of the Firefox 3 codebase, available for download.  The key advancements being touted with the beta release are performance, security, the user interface, favorites management and general feature enhancements.

I’ve yet to give Flock a try myself, but this may be the time to do it.  Flock 2.0 Beta 1 is available for download for Windows, Mac and Linux.

Tags: Beta, Favorites, Features, Firefox, Firefox 3, Flock, Flock 2, Linux, Mac, Performance, Security, Twitter, User Interface, Windows