Browser Testing Sequence

Here is an interesting post on what one web developer does to test a site in all of the relevant browsers.

I think that it’s a good general description of what browsers you should test and things to be looking at in each test.

For instance, some of the older browsers (like IE 5.5 and IE 5) aren’t worth your time to make the site look perfect in them. It is however probably advisable to at least make sure your site is still readable and useable in them (even if that means stripping out the JavaScript and CSS).

Generally speaking, this is about the same process that I follow. I’m not nearly as vigilant with all of the smaller browsers though:

When something major (a full page template or a particularly tricky part of a design) is done I give it a quick check in the latest version of every browser that runs natively on Mac OS X. Currently that means Camino, Flock, iCab, Netscape, OmniWeb, Opera, SeaMonkey, Shiira, WebKit Nightly, and any other newcomers.

Nerdy Code Examples

Usually when you’re trying to learn some programming language, you end up suffering through some pretty lame examples of code.


function Card(name,address,work,home) {
  this.name = name;
  this.addres = address;
  this.workphone = workphone;
  this.homephone = homephone;
  this.PrintCard = PrintCard;
}

Sure, it gets the point across, but man is that boring. I think I’ve seen 20 examples of this in different books and tutorials.

A couple of weeks ago I was reading a chapter from some book about Javascript objects. I was really struck by how cool the code example that they used for the chapter was. The chapter was about objects in Javascript (which, coincidentally so was the above example).


var jetpack = true;
var robot = {   
  name: null,
  hasJetpack: jetpack,
  model: "Guard",
  attack: function() {alert("ZAP!");},
  sidekick: {
    name: "Spot",
    model: "Dog",
    hasJetpack: false,
    attack: function() {alert("CHOMP!");}
  }
};
robot.name = "Zephyr";

robot.sidekick.attack();

I just love this example1. It’s so incredibly nerdy and perfect. I mean, usually with these object examples, the code is completely arbitrary. It doesn’t actually do anything, it’s just there illustrate a point. The more visual the example, the better. I’ve decided that all coding examples that are necessarily arbitrary should at least be about something interesting, like video games or robots.

  1. Yes, I understand that the coding style of this particular example is a little bit, well, ugly. I’ve just taken the example completely out of context. I believe this particular chunk was meant to illustrate something about literals. I was just so taken with the subject matter of the example…


appointive
appointive
appointive
appointive