Archive for April, 2008

A change of scenery (for a little bit at least)…

I’ve recently decided to take a break from web development probably for a couple of months. One of the reasons for this is that I’m starting to feel very burnt-out (I haven’t had a break for more than a month in three years), and the time has come to get a change of scenery for my own sanity!

My tasks for my time off are as follows:-

  1. Get super fit like I was a couple of years ago before a little thing called ‘work’ came along.
  2. Go visit my mates who are at uni

CSS3 ‘box-sizing’ article updated

Following on from the recent CSS WG F2F where issues relating to the concept were either resolved or noted, and from some email correspondence with Dave Hyatt, I’ve carried out an update to the article.
CSS3 ‘box-sizing’ article

CSS WG F2F in San Diego - feature resolutions aside…

A recent post on CSS3.Info regarding the CSS WG F2F in San Diego nicely sums up resolutions relating to possible up-coming CSS features.

Two resolutions that the post doesn’t mention however, are to do with the public disclosure of dialogue within the Working Group relating specifically to IRC log’s and meeting minutes.

It was decided that from now on the WG’s minutes and also IRC logs will be made public; there was also talk about opening up process-related discussions into a new public mailing list, although this has apparently been put on the back burner for the moment.

Euuurrggghhh! What’s going on in Safari 3.1?

Just noticed this…
safari31screenshot.jpg
….and this font-size inconsistency (Safari 3.1 overlaying FF 2.0.0.12), both in OSX
safari31screenshot2.jpg

Look’s like a couple of regression bugs as they certainly weren’t there in 3.0- think I’ll need to come up with a test case or two.

Why are we trying to re-invent the wheel?

Today, Peter Gasston posted an article summing up a recent post from Daniel Glazman talking about possible future extensions to CSS, and in particular Symbolic Constants.

I’m really trying to get my head round why this proposal was put forward (possibly because I’m particularly tired tonight and am missing some blatant advantages, in which case someone please point them out to me), but I’m really not sure why we’re trying to turn CSS into a programming language (see last two lines of Appendix E).