Browsersphere

After reading an article over at the SiteCrafting Blah Blah Blog about different ways to alternate table row colors, it occurred to me that the nth-child approach was not mentioned.  Way back in 2004 I had implemented a ridiculous (hindsight is 20/20) proof-of-concept around implementing tables without using the <table> tag.  However ridiculous the prototype might have been, one touch I added was the use of the nth-child pseudo-class to display alternating table rows in a different color.  Here’s what I wrote about that at the time:

This rule is actually a part of the CSS3 selector set, and if your browser was capable of rendering it correctly (I’m willing to bet it isn’t, at least at the time of posting) you’d see alternate background colors on the table rows (alternating between white and light gray).

Remembering that old proof-of-concept today, I decided to have another look at it.  I was disappointed to find that even in the latest version of Firefox (version 3), over four years later, the alternating row colors were nowhere to be found.  I was happy to see, though, that the latest versions of Opera (9.51 at the time of writing) and Safari (3.1.2 at the time of writing) actually do display the alternating table row colors.  As one might guess, IE7 falls in the Firefox camp on this one.

It’s unfortunate that only half of the major players support this useful feature, but I’m guessing we’ll see support added in Firefox 3.1, of which there is a first alpha targeted for release at the end of this month, since that particular release is meant to include a slew of CSS support geared toward Acid3 compliance.  Furthermore, one can hope nth-child support will show up in IE8, but that may be the least likely scenario between the two.

An article titled Check the Security Status of Browsers with Opera Widget reads a bit like something coming directly out of the Opera marketing department.  The article covers an Opera widget called Stay Secure that refreshes based on the latest data from Secunia every hour to show you a graph like the following indicating the security levels of Internet Explorer, Firefox, Opera, Safari and Konqueror:

I say the article reads a bit like a release from the Opera marketing department, because assuming Opera views Firefox as a competitor, the widget screenshot shown in the article and statements like “the test showed that Firefox 3 was [the] most vulnerable one and Opera the least” seem a little biased.  Was this actually a test, or did it happen to be the state of security at that moment the screenshot was taken?  For example, above it looks like Internet Explorer and Konqueror are the two most vulnerable.

Regardless, it seems like a neat little widget for those who like to follow web browser security closely, as long as you’re willing to use Opera to track it, since the widget is Opera-only at present.  For those like me who dabble among various browsers, this isn’t an issue.

Anyone know of similar features/extensions for other web browsers?

Since my last installment of Around the Browsersphere was posted back toward the beginning of May, there’s simply way too much going on to get all caught up without breaking things up a bit.  Therefore, this eleventh edition will focus solely on the “minor players,” or the web browsers not named Firefox, Internet Explorer, Opera or Safari.

Avant

• There’ve been about four builds (builds 17-20) of Avant Browser 11.6 released in the past month.
• The Download Blog recommends Avant Browser for “XP users who want a Microsoft-based engine but think that Internet Explorer 7 is a pain.”
• A commenter at Lifehacker points out that Firefox 3’s new fullscreen mode is old news to Avant users.

Flock

• A Mac OS X user moving away from Firefox was pleasantly surprised by and subsequently switched to Flock.
• The Flock blog has announced support for a “deeply localized” version of Flock for German users.

Konqueror

• Linux Hater’s Blog, which I was referred to via Ben Goodger’s blog, rips into some of the usability shortcomings in Konqueror.
• Ruben Schade wonders why the evolt browser archive doesn’t include past versions of Konqueror.
• An Ubuntu user is trying to figure out how to clear Konqueror’s find file history.
• Tork allows you to browse anonymously in Konqueror (and other browsers?).
• Someone thinks that the folks who are triaging Konqueror bugs are contributing to more bugs being fixed than opened in KDE recently.
• Karpion is a Konqueror add-on that “utili[z]es the Open Phishing Database to provide the user with information and tools that help protect against phishing.”
• Someone thinks IE gets something right that Konqueror doesn’t…but that’s about all said person has to say.
• A site called Echoes explains how to add new web shortcuts in Konqueror.
• In a review of Konqueror 3.5.9, the same site calls Konqueror “the great Swiss knife.”
• Over a month ago, Konqueror got support for crash session recovery and session management.

Maxthon

• A sometimes-on-the-verge-of-incomprehensible blog (case in point) suggests that Maxthon is the mathmatical equivalent of IE added to Firefox.
• Maxthon’s CEO, Jeff Chen, has been quoted as saying that they are working on porting Maxthon to Linux (via Maxthon Blog).
• One user thinks Maxthon may be a good browser for translators.
• Another user thinks Maxthon and Firefox have different core goals.
• Someone created a Maxthon logo in “cool” colors.
• There’s a list of requested features from Maxthon 1.x that aren’t in Maxthon 2 in the Maxthon forum.
• Here’s some information on where you can go to chat with fellow Maxthon fans/users.
• Here are some interesting opinions stated as facts, if you’re into that sort of thing.
• Rod Trent was counting down the days ’til he could stop using Firefox 3, but he has enjoyed using Maxthon.
• This blog suggests that Maxthon is the best alternative to Internet Explorer.
• Here’s a friendly discussion on the differences between Maxthon Classic and Firefox 3 and Maxthon 2 and Firefox 2.

SeaMonkey

• The SeaMonkey team has started having semi-weekly status meetings.
• SeaMonkey 1.1.10 was released last week.

Others

• In a request for feedback on Avant, someone mentioned Deepnet Explorer, which claims to be “the world’s first browser with RSS news reader, P2P client integration and phishing alarm.”
• Orca Browser, which has been covered here previously, appears to have resurfaced a week ago as a form of Avant utilizing Gecko 1.9 - the same rendering engine used in Firefox 3 - as opposed to Avant’s use of the Trident rendering engine from Internet Explorer.
• Web Worker Daily points to the Off By One Browser, which has “a footprint of about a megabyte.”  I think I may have mentioned it here before because I recognize the website, but it doesn’t hurt to drop its name here again.

I’m hoping to catch up on the major players soon, so stay tuned.

Apparently because I was downloading versions of Firefox 3 before it was officially released, I’ve been automatically enrolled in the Beta Testers Program.  Because of that, I was notified via a toaster notification tonight that Firefox 3.0.1 beta (build 1) is now available for testing.  I’m posting this from the new version, which identifies itself as follows:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1

If you aren’t a part of the Beta Testers Program you can download the new beta build, or if you’re just curious what it’s all about, you can head over to the mozilla.announce.prerelease newsgroup or take a look at the MozillaWiki page.  However, I’ve taken a look at both and I’m still not quite sure what the new release is all about.

A couple weeks ago I posted to Twitter about how my wife’s first impression of Firefox 3’s Awesomebar was that she hated it.  Tonight, I got a reply from the @awesomebarhate Twitter account letting me know that Awesomebar “hate feedback [is] welcome” over at Get Satisfaction.

I’m pretty sure my wife has adjusted at this point, but if you haven’t, now you know where you can go to vent some frustration or, better yet, take care of the problem.

In a few blog posts I’ve read recently, I’ve witnessed at least two backers of separate web browsers claiming that their respective browsers have an edge over Firefox because they don’t require all the add-ons Firefox does in order to behave the way a user expects them to.

First off, over at the Maxthon Blog last week, a Maxthon user was quoted as having said the following about Firefox 3:

I’m sure Firefox has add-ons that can compensate for its apparent lack of features but…my hard drive says it was nice knowing you but you have to go.

Given that the Maxthon Blog reminds me of a certain other source of information, I took the opinions there with a grain of salt.  However, I soon spotted a similar refrain at a much more trustworthy source.

Opera Watch has an article titled Guardian: Forget Firefox - I’m going back to Opera for browsing and email which quotes The Guardian columnist Andrew Brown as having said the following of Firefox 3:

With the release of Firefox 3, I mounted a private celebration: I went back to using Opera 9.5 as my main browser. This wasn’t just perversity. Firefox without its add-ons is clearly inferior to Opera. Firefox with enough add-ons to make it really useful is very much slower.

Although the reasoning behind Firefox’s add-on architecture has been well-publicized by Firefox spokesmen like Asa Dotzler and there are obviously those out there who appreciate that architecture, it appears that the latest approach by those supporting other web browsers is to suggest that the add-ons approach to feature support contributes to both a lackluster default set of features and excessive bloat once the desired features have been added.

So what’s your take?  Is Firefox’s add-on approach the right approach, or is it better to try and target a larger set of features out-of-the-box?

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.

The following is a picture of the cake the IE team sent over to the Mozilla folks when they shipped Firefox 3:

And the following is a mashup of the IE logo and the acid code (presumably from the Acid3 test?) via Twitter:

Here’s wishing a fun Fourth of July for all you American browserphiles out there.  I was hoping to link to some American themes for Firefox or Opera, but apparently there aren’t any out there (that I could find, anyway).

So instead, you’re stuck with this, which is the best I could come up with:

Just ignore the “25 million” and enjoy the fireworks tonight!

Every now and then my wife finds something to contribute to the site.  This is one of those findings:

Courtesy of I Can Has Cheezburger?