Browsersphere

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.

Just caught wind of this via Twitter:

Thanks to all the hard work of the Mozilla community as of 9:15 AM PDT today we are code complete for Firefox 3 Release Candidate 1 (RC1). New nightly builds are available - if you are a nightly tester/Minefield user you can help test these builds by selecting “Check for Updates” from your help menu.

Assuming no new issues are found today the build team will start official prep work for Release Candidate 1 (RC1) tomorrow. QA will start their extensive RC1 test pass on Monday. If all goes well we should have the Release Candidate publicly available in late May.

RC1 is intended for wider scale public testing. Our 1.2M+ active beta users will automatically get updated to RC1 when it is released. If no new showstopper issues are found in RC1 it will become Firefox 3 final. If we find any critical issues we will continue to release new Release Candidates until we are ready for final ship.

Source: Mozilla Developer News

For those interested in the development of Latitude, which was covered here in the past, be sure to check out the new official website at latitudebrowser.com and a very informative interview with the Latitude team over at Mac Fanatic.

I stumbled upon Firefox 3 Memory Usage via Twitter tonight.  The post, from Mozilla software engineer Pavlov, goes into great detail about many of the various memory usage-related changes and fixes that have gone into Firefox 3.  Those changes include, but are not limited to, reduced memory fragmentation, cache tuning, image data storage improvements and memory leak reduction.  Be sure to read the full post if you’re interested in those gory details.

According to Dave Hyatt, the Safari team has made significant gains of late in achieving compliance with the new Acid3 test.  Apparently they’ve made the leap from scoring 39/100 on the test to 90/100 after addressing issues with CSS3 Selectors, general parsing bugs, SVG and DOM Level 2 features.  According to Hyatt, the remainder of the issues tend to fall into the SVG category, and since they are getting so close to Acid3 compliance, they will be updating Surfin’ Safari regularly with updates on their progress.

As promised, I sent some questions to Sebastiaan de With, the icon and interface designer who came up with the idea for a new web browser, Latitude, which was covered here at Browsersphere recently.

Sebastiaan was kind enough to come back with very thorough and informative answers, so I’ve posted them here in full, with a few minor edits and links added.

Has the idea for Latitude been lingering in your mind for a long time, or is it something that sprang to life only recently?

I’ve been thinking about browser interfaces since the last few months, mostly inspired by the expressions of Mac users about the lack of a Mac-experience in browsers like Firefox and Flock. Although most people consider an .app bundle adequately ‘Mac-like’, I think it goes down to the very mental model the user has of the software he’s using. Take, for example, Safari’s bookmark management. There’s this great bookmark bar, that lets you toggle between the bookmark view and your website. It’s a tiny button that usually confuses some novice users I know, but I can understand that’s no priority. However, the same kind of view pops up if you access ‘History’ from the menu. It’s something a lot of users find confusing, because these completely different content views are all accessed from different places and are dismissed differently (discounting tabs and undo). Firefox also does this wrong, using a separate sidebar for anything you might be able to imagine. No user wants to think “in what sidebar is this thing I need?”

There [are] two options to improve on Firefox’s models; you either take away all the crud, without reinventing the basic principle (Safari’s path), or you re-think browser interfaces from scratch, keeping in mind the paradigms of Mac OS X, and for example iTunes. Why can my mother buy a song in iTunes, while she can’t find a fun movie on the internet, or keep track of what’s happening in the world?  It then struck me that original ideas should be implemented to reduce the screen estate the interface would consume, and the pieces of the puzzle soon clicked together. What do you want in a browser? I’m sure I could ask any intermediate computer user and get a list of his most wanted features. Now try condensing that into a new browser, with the basic premise that the UI should be minimal.

In your “My dream browser” post you wrote “I am aware of several ‘new generation’ browser projects, but none really line up with my ideas.”  Can you share a few of these “new generation” projects and/or why you think they fall short?

The two projects that really [caught] my attention were Flock and Shiira; these two browsers are ideologically opposed to each other. Flock tried to make an integrated browsing experience and failed, in my opinion. The Mac version of Flock once counted no more than 10 buttons; these days, its toolbar is chock full of nondescript buttons and widgets. To me, it wasn’t just visually busy, but it was mostly a browser that seemed like a big hassle to get my head around. I just want something I don’t have to learn, while still being feature-packed. Shiira really did much better in this regard, but simply went a different direction, reinventing parts of the interface, making things more intuitive and visual, but in no way expanding on the feature set of browsers. I really want both; an intuitive browser that’s as functional for viewing web content as the Finder is for viewing files on your disk. Finder doesn’t just handle one format of files either; it can handle your content. And in my opinion, that’s what a browser should do today. Focus on content.

The feedback to both of your posts on the subject has been very positive based on the comments.  Have you gotten a lot of other feedback through email or by other means, and has it been just as positive?  Are there any instances where you received constructive criticism or even negative feedback?

I’ve gotten a lot of email from developers and people who really want to see this developed. I chatted with a few developers, but as I’m very occupied as a full-time icon and interface designer, I can’t oversee or manage such a project right now.

I’ve gotten more than enough constructive criticism and even negative feedback; from people saying my interface mockups are just ‘someone with Photoshop‘ to dismissing certain ideas or even calling me names for proposing to take away the tab bar when the sidebar is active. I think a lot of people misinterpret my designs; most think it’s intended to completely throw every interface paradigm in browsers today overboard, but that’s the opposite of my intention.

I want to make a browser with a more accessible and less cluttered interface. For loose ideas, like the ‘Time Machine’ view for history I mocked up, criticism is fierce, while I’ve always mentioned that it is just a mock-up of a more visual way to view your history for one website, suggesting a different view for all website history. But most people who express the most intense critique fail to offer any real better solutions to the problem.

In your “Latitude” post, you wrote “Several developers have contacted me with the desire to develop it, and some have already actively begun programming whole aspects of it.”  Can you share what aspects have already gone under development?

Thanks to Apple’s WebKit, developers are able to implement a multitude of my interface ideas and gauge the feasibility other features I suggested . Currently, basic work is being done on making more intelligent sidebar behavior, fullscreen browsing, and changing things like Downloads and Bookmarks from their conventional format to something ready for the sidebar.

Will you be making the design document and centralized website you mentioned in that same post available for public consumption, or are you trying to limit it to only those actively working on the project?

I intend to make this as open as possible, and I hope all developers working on the project are eager to allow other people to chip in and collaborate to make a better browser reality.

I noticed some criticism of Firefox in your other blog entries.  Is this your primary web browser today?  If so, what do you think are its biggest shortcomings?

Although Firefox is not my primary web browser (Safari is), it is one of the most used browsers today, and the last beta version for OS X showed an interface that is absolutely nonstandard and horribly designed. I think Firefox, while aiming for a ‘good’ look and feel on all platforms, really fails to deliver on any, with perhaps the notable exception of Linux. As I said in the response to your first question, the lack of invention in the interface causes the user to go on a quest to find the features he needs, and disappoints most of the time in providing them.

Have you put any thought into working your visual design ideas into an already existing platform (e.g. Firefox) via extensions or themes in order to bypass all of the work that goes into creating a new rendering engine, etc.?

As I said in my response to question 4, WebKit already allows this, and thanks to that, I can deliver the interface in full Cocoa glory. Firefox (with the exception of Camino) still uses XUL to render its interface, which is something I wouldn’t want to touch with a ten foot cattle prod. Also, I think drastically changing the structure and interface of a browser like Firefox would require so much more than an extension, that working ‘from scratch’ is automatically the preferred option.

If readers of Browsersphere are interested in contributing, what kinds of help are you looking for?

Anything! If you can code a website, feel free to drop an email, but especially (talented) developers are encouraged to contact me to get details on the project before the official website goes live.

Anyone who has downloaded Firefox nightly builds is likely familiar with the Minefield moniker that replaces “Firefox” wherever that application title is used in a typical Firefox build.

I have been testing the latest Minefield builds the past couple of nights, and tonight I was notified of an update and subsequently downloaded it.  In the new version, which is identified by the following user agent string:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2008012804 Minefield/3.0b3pre

…the new Firefox theme icons have started to appear.  These changes were recently alluded to in a post by Alex Faaborg.  As of the latest build, the reload, stop and home icons have been updated.  The back and forward navigation buttons have yet to change, presumably because work is still being done on the new Keyhole design and functionality.

The icons that have changed look exactly as presented at Alex’s blog.  Unfortunately, I have to say that I’m not a fan of the change.  Perhaps once the Keyhole changes are in place things will flow a little better, but the new icons have a bit of a “childish” feel to them that I just don’t like.  However, having once been a Firefox theme developer, I know all too well that everyone has their own, often very strong, opinions one way or another about the various Firefox themes.

Given that, what do you think of the change?  Furthermore, what do you think of the new Keyhole approach?  If you haven’t had a chance to see them in action, give one of the latest nightly builds a try.  Minefield is stablizing at the moment since Mozilla is getting close to releasing a third beta of Firefox 3.

If you’re as into following web browsers as I think you are, you probably already heard that an internal Microsoft build of the next version of Internet Explorer, which will be dubbed IE8 (and not something else), recently passed the Acid2 test.  The news spread quickly, as it was featured on sites like Slashdot and Digg, and was relished, praised and congratulated by many, and met with some criticism by others.  Robert Scoble gave kudos to Microsoft and the IE team; Opera Watch called it an “exciting and positive step in the right direction for Microsoft and the Web;” Simon Willison gave some technical examples of what the news means, Slightly Ajar called the news “a great win for standards;” Dave Shea called it a “huge leap forward.”

On the more skeptical front, both Asa Dotzler and Slightly Ajar questioned just what exactly the IE team meant when they referred to “IE8 standards mode.”  Furthermore, Dave Massy responded to some criticism and other questions about the forthcoming browser.  When Bill Gates was asked about some of the secrecy that has surrounded the release in a recent interview, he expressed surprise and allowed that there aren’t any deep secrets about what is going on with the development of the browser.

To say that all the recent ramblings have gotten people talking about the browser would be an understatement.  Beyond sparking interest in IE8’s handling of the Acid2 test, the buzz has spurred ideas and suggestions about what other features should be included in the release.

If you’ve gotten through this post and you’re still itching for more information about IE8, which is reportedly due out in the first half of this year, the original announcement at the IEBlog is packed with details, including the checkin log from when the feature landed in the central IE build, a Channel 9 interview features IE GM Dean Hachamovitch and Architect Chris Wilson, and a post titled IE8 Expectations, written by Jonathan Snook, is one of the better written posts on the subject, including everything from details about the underlying Trident rendering engine to predictions about what will and won’t be supported.  So be sure to give those links a read as well.

The following comes from CSS3.info:

Dave Hyatt has recently checked in to the WebKit repository some basic support for using the ClearType text rendering system, which uses a different algorithm for subpixel anti-aliasing than the current CoreGraphics libraries do. Windows users will find that this makes text in Safari look similar to text in other web browsers and elsewhere on the system.

For more information on some of the caveats of the new feature and how you can try it out yourself, be sure to read ClearType rendering forthcoming for Safari on Windows? in its entirety.

I created a rather lengthy post over at my personal blog tonight titled How to Contribute to Firefox.  Rather than cross-post it here, I figured I’d at least share the link, since it’s probably relevant to a lot of the readers here (or at least I hope it is).