Safari so goodie (sorry)

Following the launch of Apple's new Safari browser, I echo Ben's astonishment at just how quick Gordon Byrnes released his Safari Enhancer app. Good Lord!

I've continued to use Safari, and I'm pretty impressed. I would reiterate that it. is. in. beta for the whingers though…

Ed wanted to know what the standards compliance was like and I'd say the basic stuff is pretty good. Mark can tell you more. There certainly doesn't seem to be a need for any widespread panic along the lines of "Oh God, another browser to support." Not if you code right, and bear in mind improvements are sure to be made before v1.00. For a start, they can stop that "like Gecko" identification! (Although for the record, Safari Enhancer can help address this).

Moving on, a few minor tweaks to this site. As noted yesterday, all my links (Domino blogroll, "normal" blogroll, geek sites, etc., etc.) are now in a view, and I've added a load more. I shall keep 'em coming, but the Domino blogroll was my priority! What else have I been doing… well, I've continued categorising my blog entries. Nearly all done. This is for a new "Related reading" feature I'll soon implement for the blog. My apologies if this screws up any RSS feeds' unread marks, although you should be OK as I've been categorising for a month or so already, and the feed only comprises the current month's blog entries.

Later: Dave Hyatt clarifies re the user agent string in Safari. It makes sense, but must be annoying for the Konqueror and Safari teams! As Dave says:

We chose to be more like Gecko than like MSIE because we wanted to be lumped into the standards compliant category, because fundamentally we are committed to supporting DOM 1&2, CSS1&2, and enough proprietary MSIE extensions and Gecko extensions (innerHTML, createContextualFragment, offsetWidth/Height, etc.) that we could be placed in a similar category.


  1. Don't apologise. Top punning.
    "and enough proprietary MSIE extensions"
    Does that mean non-standard IE browser war markup tags? If so, they shouldn't bother. Browser makers have a responsibilty to support standards, they have no responsibility to support IE, or to support developers/designers that like marking up using special IE tags. It's up to us developers/designers to not use such tagging. I understand the commercial reasons for browsers supporting suchlike, but it's not the way, surely?Tone#
  2. You have a point Tone. That very argument is being thrashed out as we speak. Check out Dave Hyatt's blog, in addition to Mark Pilgrim's for more discussion.

    I suppose the thing to bear in mind is that some M$ extensions and custom tags do make it into the standards, when it makes sense. Consider how Mozilla supports innerhtml for example.

    Anyway, Dave has an interesting take on why some things should be supported, and Mark talks about whether certain CSS "hacks" should be used / ignored / whatever in his blog.

    Thanks for dropping by — good to see lemansworld is up and running too!

    Ben Poole#

Comments on this post are now closed.


I’m a software architect / developer / general IT wrangler specialising in web, mobile web and middleware using things like node.js, Java, C#, PHP, HTML5 and more.

Best described as a simpleton, but kindly. You can read more here.