I realize I may not be your average browser user. As a web developer, a browser to me is two parts daily use, two parts testing, and one part challenge. Since 2005, I've been using Firefox in some form or fashion as both my primary browser and as a testing vehicle.

I had recently started a JavaScript-intensive project, and I appreciated Safari 4's lightning-fast JavaScript execution speeds. In Firefox, I rely mostly on add-ons like Web Developer and Firebug to help me analyze and test for mistakes in websites I build in Firefox. They work great, but enabling them slows the browser down.

That's why I was excited for the updated Web Inspector that comes as part of Safari 4. (Yes, Safari 3 first came with Web Inspector, it couldn't hold a candle to Firebug's Swiss Army knife of an add-on for Firefox.) Testing was easy, and Safari 4's Web Inspector's many improvements made me think I could migrate to Safari full-time.

Read on to see how it went.

Do you feel the need... the need for speed? With more and more of our computing lives taking place via our web browsers, eking out even a slight performance improvement for Firefox or Safari (or a similar reduction of resource demands; I'm looking at you, Flash Player) can improve the user experience noticeably. One way to improve browser performance, if you've got the chops and the time, is to compile the open-source browser of choice yourself, with all the tweaks for the specific processor platform you're using.

Web guru Neil Bruce Lee has offered the performance-hungry Firefox user the choice of G5 and Intel optimized versions of the 3.0 release; now, for those who want to live completely on the far side, Chris Latko has rolled out an Intel-optimized build of the beta Firefox 3.1 (Shiretoko) browser. With the architecture-specific tweaks Latko made, along with the inclusion of the TraceMonkey Javascript native compiler, this is the screaming-est version of Firefox ever to grace an Intel Mac screen... but be wary, it's going to be less stable than an official release, and many of your favorite plugins may not work (best to disable them all in the 3.0x version, then enable one at a time in the beta build to make sure they play nicely).

Don't roll the Firefox way? There's a bleeding-edge choice for you too: WebKit nightly builds, based on the most current code that goes into future versions of Safari. Again, you should see a boost in speed and possibly a corresponding decrease in stability, so tread with caution.

If you're running an optimized browser build, share your experiences with us below.

Thanks Chris!

[Hat tip: Mac.Blorge]

New nightly builds of Safari's bleeding-edge doppelgänger, WebKit, are getting some new support for CSS animations -- support that's already available in MobileSafari.

The animations, which include a falling leaves effect, a way to simply animate objects sliding across the screen, and a "pulse" effect (described as "the new <blink>") are all supported by WebKit. The WebKit blog shows code examples about how to use these behaviors in your own sites.

MacRumors's Arnold Kim suggests that Apple may be looking to obviate the need for Flash on the iPhone and iPod touch through the implementation of web tools like CSS Animation. I would argue that while CSS is powerful, getting Flash on the iPhone is about one thing and one thing only: Games.

One shining year -- that's how long the iPhone-optimized iGoogle search page hung around, and now we must tell it goodbye. Introduced in January 2008, the customized iGoogle UI for Mobile Safari provided a single-column view and easier navigation for iPhone users. As Christina noted earlier today on Download Squad, the sleek UI has been replaced with the unified mobile format for iGoogle that renders similarly on most mobile browsers, including Google's own Webkit-based Android browser (which previously had benefited from the Webkit-tweaked front page for the iPhone).

The unification of the mobile iGoogle interface may simply be an effort by Google to level the playing field instead of having the iPhone as a most-favored-device, or it might be part and parcel of the big G's shaving down on costs by eliminating offerings like Jaiku, Dodgeball and Google Notebook. Either way, if you're mourning the loss of your custom iGoogle look, let us know below.

Earlier this week, there was a sudden influx of web browsing applications in the App Store. Mac Rumors points out that some of them, most notably Edge Browser [App Store link], have very old release dates even though they only showed up in the store recently (Edge Browser's release date is listed as Oct. 13, '08). It's important to note that these aren't true third party browsers, but enhancements to Mobile Safari.

What's interesting is that Apple has previously rejected applications for "duplicating functionality" of some of their own software. Specifically, Podcaster was rejected because it "...duplicates the functionality of the Podcast section of iTunes," while MailWrangler was denied for duplicating "...the functionality of the built-in iPhone application Mail without providing sufficient differentiation or added functionality."

Perhaps Apple is now loosening the reigns a bit. Applications like Edge Browser, Incognito [App Store link], QuickSurf [App Store link] and WebMate: Tabbed Browser [App Store link] offer web browsing functionality in one form or another. For example, Incognito allows for history-free browsing, QuickSurf speeds things up by omitting most images and WebMate queues up all links for later viewing.

Sure, they aren't full fledged, third party browsers, but it's baby steps we're after.

[Via MacDailyNews]

Sparkle, Andy Matuschak's software update framework for Cocoa applications, is no stranger to TUAW. Now, it's found its way into WebKit, the developmental version of Safari. This feature, often requested on the WebKit mailing lists, allows WebKit to update itself with the click of a button.

Sparkle has become a standard for Mac applications. I tend to shudder a little bit every time an application has the smarts to tell me there's an update, but then sends me to a web page to download it. Not because I'm lazy, just because I know there's a better way. There are several variations cropping up, including one from Google. I haven't worked with the newcomers, but I can testify that Sparkle is so utterly simple to implement that developers who fail to do so should be scolded repeatedly until they capitulate (see WebKit). A hearty thanks, though, to the WebKit team, from all of us who surf the bleeding edge of browser development.

Thanks to Chris Pirillo for the tip!

I was really disappointed when Google released their Chrome web browser for Windows only. When it comes to browsers, I've tried them all. Right now I regularly switch between Firefox and the latest nightly build from Webkit (essentially Safari). Firefox has the extensibility I rely on, while Webkit has the performance I crave. I had hoped that Chrome would magically combine those two crucial traits and become my new go-to browser. Unfortunately, Chrome is not yet nearly as extensible as Firefox, and isn't available for Mac (yet).

So imagine my surprise when I stumbled upon the latest experimental Firefox build from Mozilla, called Minefield. This Minefield should not be confused with the unofficial optimized builds of Firefox that Brett wrote about, which are also referred to as Minefield. Minefield is Mozilla's code-name for this generation of Firefox, and the code name is used for unofficial builds to avoid infringing upon the Firefox name.

So, what's so special about the Mozilla Minefield build? It's fast... smokin' fast. This is essentially a version of Firefox with the new TraceMonkey JavaScript engine under the hood, and as Ars Technica reports, it tests even faster than Google's V8 JavaScript engine.

As most Mac users have noted, Firefox is kind of pokey on the Mac platform, particularly compared with WebKit or even Safari, and even when compared with Firefox on a similarly spec'd Windows machine. Version 3 of Firefox was supposed to fix the performance problem, and while it's somewhat better, it's still not great.

Well, Minefield is great. Using Gmail or even a complex content management system is a breath of fresh air. I feel like my web apps are finally keeping up with me.

There's one caveat, and it's a big one: though the current version number is 3.1b2pre (the "b" denoting beta status), this is really alpha software. That means there will be bugs, and you will experience problems. Surprisingly, though, Minefield has been very stable in my testing -- not yet crashing in a full day of testing. I have restarted it a couple of times due to suspicion that something strange was going on, but I can't say for sure if it was.

If you use it with your regular Firefox profile rather than creating a new one, Minefield will complain that most of your extensions are not compatible. Using Nightly Tester Tools, I re-enabled all of the extensions that it disabled, and every single one of them appears to be working normally, even the complicated ones like Better Gmail 2 and TabMixPlus.

I've only had a problem with one site so far, but unfortunately it's a big one: Google Docs. The page simply won't load. But for now, I'm willing to open WebKit or Camino to edit my Google Docs, because I'm just too smitten with the raw speed that Minefield offers.

One last note: being a nightly build, you will likely find that new versions are available, well, nightly. Mozilla makes the process of upgrading to the latest version virtually painless by using the built-in version monitoring process that Firefox uses.

[via Ubuntu Unleashed]

The Omni Group has released version 5.8 of OmniWeb, its venerable browser software.

OmniWeb 5.8 is now based on the same version of Webkit as Safari 3.1.x. It also fixes bugs with Spaces, and adds support for non-POSIX file URLs. Users can also choose Google Chrome in the list of user-agent strings. Full release notes are also available.

OmniWeb 5.8 is available from Omni's website, and works with Mac OS X 10.4.8 or later. The software is $14.95, with upgrades starting at $4.95 for users of Omniweb 4.

Even though Google Chrome is still only available for Windows, its WebKit roots mean that Safari for Mac users might still get some extra perks. Gears, Google's web API that lets developers create applications that can run offline, is one of those perks. Previously, Gears was only available for Firefox on the Mac, and it certainly didn't feel like there was any priority in bringing Gears to Safari. Well, with Google's gung-ho dedication to all things WebKit, the Google Mac team has just released Gears for Safari.

Even better, for WebKit browsers on the Mac that are not Safari, Google has made it easy to implement Gears without having to use InputManager. Fluid, a site-specific browser (it basically makes it possible to treat a web app like a regular app), implements Gears this way.

Gears for Safari requires OS X 10.4.11 or 10.5.3 or higher. You can download it here. After you install Gears, check out Google Docs, Zoho or Remember The Milk offline. It's pretty awesome.

Although Google's Chrome browser is currently only available to Windows users (unless you are running an Intel-based Mac and VMWare Fusion or Parallels), its WebKit underpinnings mean that Safari, and other WebKit-based browsers, can benefit from Google's code.

One of the larger innovations of Google Chrome, the V8 JavaScript engine, is incredibly fast. The WebKit project has its own new JavaScript engine, SquirrelFish, used in Mobile Safari and the WebKit nightlies. Still, the code base for V8 along with the Skia graphics library are making their way into the main WebKit repository. The Skia graphics library may already be in some of the newest nightly builds.

What does this mean for Mac and Safari users? Superficially, it might mean very little for right now, however, the Safari team can choose to implement any of the Chrome features that have been added back to the repository. That's the beauty of open source.

Google is developing a new web browser built from the ground up and based on WebKit, the same rendering engine that Safari uses.

The browser, called Chrome, is open-source software built with security, compatibility and speed in mind. Each tab in the browser will be its own separate running process. For example, if JavaScript hangs in one tab, the other tabs will remain unaffected. The approach is similar to the way Mac OS X isolates applications in their own private areas to prevent one crash from taking down the whole system.

Google picked an interesting way of announcing the project: They commissioned illustrator Scott McCloud to draw a 38-page comic book about the project, and distribute it under a Creative Commons license. The result is a very readable, fascinating way to learn about the new browser.

For web developers, Chrome will include strong Gears integration, and a JavaScript virtual machine that generates super-fast machine code out of JavaScript instructions. For end users, it will include a new start page that lists the last several pages and search terms you've used. It also includes a private browsing mode.

Google is planning on formally launching the project on Wednesday, but the Chrome website isn't visible to the public yet. Update: Google is releasing a version for Windows tomorrow, with Mac and Linux versions coming soon, once Chrome is "faster and more robust." (Thanks, Bryan!)

[Via Macworld]

Apple has seeded developers with a copy of the new Safari 4, which adds some new features and is based on a newer version of WebKit. Apple is also rumored to be using the SquirrelFish JavaScript engine which allows for faster Javascript processing.

New to this version of Safari is the ability to save webpages as "Web Applications." This new feature allows Safari to save pages similar to the way Fluid does. You also have the ability to choose how new windows will open (i.e. with your favorite bookmark, blank page, etc.).

One of the biggest "features" is the fact that Safari 4 (along with the new version of WebKit) scored a perfect 100/100 on the Acid3 test. If you are inclined to see what the new version looks like, World of Apple has placed some screen grabs on their blog for your viewing pleasure.

WebKit, the open source foundation that many Mac apps use to draw HTML, seems to be preparing for some kind of operating system update in the near future.

Intrepid Flickr user factoryjoe posted an image of a screenshot showing a recent WebKit nightly build. In the Frameworks folder inside the application package, there's an alias named "10.6." The alias points to the "10.5" folder immediately above it.

What could this mean? Most likely, there's a new release of the operating system on the horizon, and WebKit developers are ready to get cracking on it. The fact that the file is a symbolic link and not an actual folder could suggest that development is either very early on at this point, or web services for the next Mac OS X are very similar to Leopard's.

Thanks, Chris!

This was included in WebKit builds beginning several years ago, apparently, but is something I recently stumbled upon. Historically, Safari has been pretty insistent on making sure web page form fields (like drop-down menus and buttons) retain the Aqua look-and-feel. Web designers, on the other hand, have gotten used to choosing colors and font sizes for those controls, so they fit in with their site's design.

Hopefully everyone can now be happy: Safari 3 allows web designers to style form controls with CSS. The results are pictured: instead of a glossy, Aqua-like control, Safari displays a matte-finish control in the color and size of your choosing. You can even apply background images to form controls. If you don't apply styles to your controls, then Safari retains the Aqua look.

This shouldn't require any changes to code that's already written for other browsers: Safari 3 should pick right up on the formatting, and display it as the designer intended. It does, however, open up WebKit-specific CSS to your form controls.

In the rather rarefied atmosphere of web standards compliance, the Acid3 suite of browser tests is like a pro wrestler's chair to the back of the head: if you can take it and keep standing, that's very impressive. The Acid3 suite, first released at the beginning of this month, pushes browsers to the very edges of their rendering, SVG, CSS and DOM scripting capabilities -- all necessary for a consistent and interoperable Web 2.0 experience.

As with the earlier Acid2 test, there's been a bit of a horserace among browser development teams to be the first to the finish line with Acid3, including the WebKit squad responsible for Safari's underlying engine; Acid3 dev Ian Hickson gives major props to Apple and the WebKit devs on his blog, including efforts to clear bugs in the test suite itself (he had to work quite hard to find standards compliance issues in WebKit). On Wednesday evening, both the Opera and WebKit teams declared a 100% score -- not a full pass, as there are minor issues to clean up, but nevertheless the test looks like it should. With the Mac nightly build of WebKit available for download, you too can feel the power of this fully operational web standards battle station.

[A quick clarification: While both Opera and WebKit have claimed 100% on Acid3, only one of the browsers -- WebKit -- has a publicly downloadable version right now that can make that score. Opera's build won't be released for another week or so.]

Thanks Adam